Triple
T30857976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20 Million Miles to Earth |
E785979
|
entity |
| Predicate | finalClimaxLocation |
P81796
|
FINISHED |
| Object | Colosseum in Rome |
—
|
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: Colosseum in Rome | Statement: [20 Million Miles to Earth, finalClimaxLocation, Colosseum in Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalClimaxLocation Context triple: [20 Million Miles to Earth, finalClimaxLocation, Colosseum in Rome]
-
A.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
B.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
C.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
D.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
E.
finalsLocation
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 29, 2026, 8:46 p.m.