Triple
T918865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Foreign Affairs of the Soviet Union |
E19835
|
entity |
| Predicate | formedAsMinistry |
P22364
|
FINISHED |
| Object | 1946 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1946 | Statement: [Ministry of Foreign Affairs of the Soviet Union, formedAsMinistry, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAsMinistry Context triple: [Ministry of Foreign Affairs of the Soviet Union, formedAsMinistry, 1946]
-
A.
ministry
Indicates that an entity serves as a governmental ministry responsible for specific public functions or policy areas in relation to another entity.
-
B.
typeOfMinistry
Indicates the specific category or kind of ministry that an entity belongs to or represents.
-
C.
hasMediaMinistry
Indicates that an entity operates, oversees, or is associated with a ministry or department responsible for media-related affairs.
-
D.
numberOfMinistries
Indicates the total count of ministries associated with or belonging to a given entity.
-
E.
hasMinister
Indicates that one entity serves as the minister (political, religious, or administrative official) responsible for or associated with another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.