Triple
T9924667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Around the World in Seventy-Two Days |
E187890
|
entity |
| Predicate | describesDuration |
P40755
|
FINISHED |
| Object | 72 days |
—
|
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: 72 days | Statement: [Around the World in Seventy-Two Days, describesDuration, 72 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesDuration Context triple: [Around the World in Seventy-Two Days, describesDuration, 72 days]
-
A.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
B.
intendedDuration
chosen
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
C.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
D.
alternativeDuration
Indicates that there is an additional or substitute time span associated with an event or activity, differing from its primary or standard duration.
-
E.
eraDuration
Indicates the length of time that a particular era or period spans.
- 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_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. |
Created at: March 30, 2026, 8:43 p.m.