Triple
T9924669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Around the World in Seventy-Two Days |
E187890
|
entity |
| Predicate | chroniclesEndDate |
P91164
|
FINISHED |
| Object | 1890 |
—
|
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: 1890 | Statement: [Around the World in Seventy-Two Days, chroniclesEndDate, 1890]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chroniclesEndDate Context triple: [Around the World in Seventy-Two Days, chroniclesEndDate, 1890]
-
A.
chronologyEnd
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
B.
chroniclesPeriodFrom
Indicates that something documents or records events starting from a specified point in time or historical period.
-
C.
chronologyStart
Indicates the point in time at which a sequence, event, or temporal record begins.
-
D.
chronicledBy
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
-
E.
tookPlaceUntil
Indicates that an event or situation occurred continuously or repeatedly up to a specified end time or date, after which it no longer took place.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb598651081908286763ff56ba57c |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:43 p.m.