Triple
T5473909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chan Chan |
E122900
|
entity |
| Predicate | abandonedAfterEvent |
P63965
|
FINISHED |
| Object | Inca conquest |
—
|
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: Inca conquest | Statement: [Chan Chan, abandonedAfterEvent, Inca conquest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedAfterEvent Context triple: [Chan Chan, abandonedAfterEvent, Inca conquest]
-
A.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
B.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
C.
repealedAfterEvent
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
-
D.
periodOfAbandonment
Indicates a time span during which something is left unused, unattended, or not maintained.
-
E.
closedAfterEvent
Indicates that an entity becomes or is marked as closed following the occurrence of a specified event.
- F. None of above. chosen
Provenance (4 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9232ded08190b4142e604319b2ba |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd9214b8488190979112c7615f359a |
completed | March 20, 2026, 6:29 p.m. |
Created at: March 20, 2026, 2:09 p.m.