Triple
T26962645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Fe (Newsies song) |
E679086
|
entity |
| Predicate | destinationDesired |
P21947
|
FINISHED |
| Object | Santa Fe, New Mexico |
—
|
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: Santa Fe, New Mexico | Statement: [Santa Fe (Newsies song), destinationDesired, Santa Fe, New Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationDesired Context triple: [Santa Fe (Newsies song), destinationDesired, Santa Fe, New Mexico]
-
A.
transportGoal
Indicates that an entity has the objective or intended outcome of moving or conveying something or someone from one place to another.
-
B.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
C.
destinationOfVoyageTo
Indicates the endpoint location that a particular voyage or journey is directed toward or arrives at.
-
D.
destinationCity
Indicates the city to which an entity is traveling, being sent, or ultimately directed.
-
E.
destinationIsland
Indicates the island that serves as the endpoint or target location to which someone or something is going or being directed.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620ede4f88190a98f91af97505663 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:32 a.m.