Triple
T25715373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Sydney |
E644847
|
entity |
| Predicate | modernServicesDurationHours |
P99305
|
FINISHED |
| Object | approximately 21 hours |
—
|
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: approximately 21 hours | Statement: [London–Sydney, modernServicesDurationHours, approximately 21 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernServicesDurationHours Context triple: [London–Sydney, modernServicesDurationHours, approximately 21 hours]
-
A.
serviceDays
Indicates the specific days on which a service is provided or operates.
-
B.
typicalTimeInServiceToAttain
Indicates the usual duration of service required for an entity to reach or attain a specified status, level, or condition.
-
C.
hasServiceTime
chosen
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
D.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
E.
serviceAge
Indicates the length of time an entity has been in service or actively performing its role.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 9:40 p.m.