Triple
T6532177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Council of the Armed Forces |
E152255
|
entity |
| Predicate | transferredPowerDate |
P34797
|
FINISHED |
| Object | 2012-06-30 |
—
|
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: 2012-06-30 | Statement: [Supreme Council of the Armed Forces, transferredPowerDate, 2012-06-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredPowerDate Context triple: [Supreme Council of the Armed Forces, transferredPowerDate, 2012-06-30]
-
A.
deFactoTransferDate
Indicates the date on which control or ownership is effectively transferred in practice, regardless of the formal or legal transfer date.
-
B.
dateOfTransferOfPower
chosen
Indicates the specific date on which governing authority or control is formally transferred from one party to another.
-
C.
lostPowerDate
Indicates the date on which an entity lost electrical power or ceased to have power available.
-
D.
dateOfConversion
Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
-
E.
deJureTransferDate
Indicates the official legal date on which ownership or rights are formally transferred from one party to another.
- F. None of above.
Provenance (3 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbe168881908ffefc4962e2893d |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.