Triple
T29778187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jornada del Muerto |
E755438
|
entity |
| Predicate | dateOfNotableEventNearby |
P123065
|
FINISHED |
| Object | July 16, 1945 |
—
|
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: July 16, 1945 | Statement: [Jornada del Muerto, dateOfNotableEventNearby, July 16, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfNotableEventNearby Context triple: [Jornada del Muerto, dateOfNotableEventNearby, July 16, 1945]
-
A.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
B.
nearHistoricalEventDate
chosen
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
-
C.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
D.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
E.
nearbyHeritageDestinations
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 8:48 p.m.