Triple
T6532150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Council of the Armed Forces |
E152255
|
entity |
| Predicate | assumedDeFactoControlOn |
P38281
|
FINISHED |
| Object | 2011-02-11 |
—
|
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: 2011-02-11 | Statement: [Supreme Council of the Armed Forces, assumedDeFactoControlOn, 2011-02-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumedDeFactoControlOn Context triple: [Supreme Council of the Armed Forces, assumedDeFactoControlOn, 2011-02-11]
-
A.
hasDeFactoControlBy
chosen
Indicates that one entity effectively exercises practical or informal control over another, regardless of formal or legal authority.
-
B.
recognizedControlOf
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control over something.
-
C.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
- 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.