Triple
T15792394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuschi, Ayacucho, Peru |
E382890
|
entity |
| Predicate | eventOccurredOn |
P830
|
FINISHED |
| Object | 1980-05-17 |
—
|
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: 1980-05-17 | Statement: [Chuschi, Ayacucho, Peru, eventOccurredOn, 1980-05-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventOccurredOn Context triple: [Chuschi, Ayacucho, Peru, eventOccurredOn, 1980-05-17]
-
A.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
B.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
C.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
D.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
E.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d9623081908496cdfdf86a078a |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.