Triple
T10094017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Liberation Front (FLN) |
E215816
|
entity |
| Predicate | monopolyOnPowerUntil |
P35133
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [National Liberation Front (FLN), monopolyOnPowerUntil, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monopolyOnPowerUntil Context triple: [National Liberation Front (FLN), monopolyOnPowerUntil, 1989]
-
A.
monopolyOn
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
B.
lostMonopolyOnPower
chosen
Indicates that an entity previously held exclusive control or authority but no longer maintains that sole dominance.
-
C.
monopolyGrantedBy
Indicates that one party has been given exclusive control or rights over a market, resource, or activity by another authority or entity.
-
D.
isMonopoly
Indicates that one entity exclusively controls a market or resource, facing no significant competition.
-
E.
monopolyEndedBy
Indicates that a previously existing monopoly was terminated or disrupted by a particular agent, event, or intervention.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05da3688190b7a1ac8a58e5488f |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.