Triple
T25715372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Sydney |
E644847
|
entity |
| Predicate | earlyServicesDurationDays |
P7618
|
FINISHED |
| Object | several 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: several days | Statement: [London–Sydney, earlyServicesDurationDays, several days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyServicesDurationDays Context triple: [London–Sydney, earlyServicesDurationDays, several days]
-
A.
serviceDays
Indicates the specific days on which a service is provided or operates.
-
B.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
typicalTimeInServiceToAttain
Indicates the usual duration of service required for an entity to reach or attain a specified status, level, or condition.
-
D.
primaryServicePeriod
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
-
E.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
- 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_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 9:40 p.m.