Triple
T36845407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zanjón |
E910529
|
entity |
| Predicate | eventConcludedAtLocation |
P187618
|
FINISHED |
| Object | Ten Years' War |
—
|
NE NERFINISHED |
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: Ten Years' War | Statement: [Zanjón, eventConcludedAtLocation, Ten Years' War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventConcludedAtLocation Context triple: [Zanjón, eventConcludedAtLocation, Ten Years' War]
-
A.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
B.
eventEndDateAtSite
Indicates that an event concludes on a specific date at a particular site or location.
-
C.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
D.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
E.
tookPlaceAtLocation
Indicates that an event or action occurred at a specific location.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: May 3, 2026, 4:13 p.m.