Triple
T10506486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concertación coalition |
E247798
|
entity |
| Predicate | firstGovernmentEnd |
P73507
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Concertación coalition, firstGovernmentEnd, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGovernmentEnd Context triple: [Concertación coalition, firstGovernmentEnd, 1994]
-
A.
formedGovernmentAfter
Indicates that one entity established or assumed control of a government following another specified event, period, or governing body.
-
B.
royalGovernmentEnd
Indicates the point in time or event at which a royal form of government ceases to exist or loses its governing authority.
-
C.
newGovernmentFormed
Indicates that a new governing body or administration has been officially established, replacing or succeeding a previous one.
-
D.
endOfGovernmentTerm
chosen
Indicates that a specific point in time marks the conclusion of a particular government's or officeholder's official term in power.
-
E.
succeededByGovernment
Indicates that one government is directly followed and replaced in power or authority by another government.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b17cd88190b37e41b3ce2b4b16 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:26 p.m.