Triple
T20053382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third National Government Junta of Chile |
E499261
|
entity |
| Predicate | locatedInTimePosition |
P81955
|
FINISHED |
| Object | before the Reconquista of Chile |
—
|
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: before the Reconquista of Chile | Statement: [Third National Government Junta of Chile, locatedInTimePosition, before the Reconquista of Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimePosition Context triple: [Third National Government Junta of Chile, locatedInTimePosition, before the Reconquista of Chile]
-
A.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
-
B.
locatedInTimeBefore
chosen
Indicates that one temporal event or interval occurs entirely before another in time.
-
C.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
D.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6633043a481908359ad232607182a |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.