Triple
T35211404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leicester Ring |
E1016688
|
entity |
| Predicate | typicalCruisingTime |
P29135
|
FINISHED |
| Object | about 1 to 2 weeks |
—
|
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: about 1 to 2 weeks | Statement: [Leicester Ring, typicalCruisingTime, about 1 to 2 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCruisingTime Context triple: [Leicester Ring, typicalCruisingTime, about 1 to 2 weeks]
-
A.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
B.
typicalStopoverDuration
Indicates the usual length of time that an intermediate stop or layover between two parts of a journey typically lasts.
-
C.
missionDurationHoursApprox
Indicates an approximate length of time, measured in hours, that a mission is expected to last or has lasted.
-
D.
voyageDuration
chosen
Indicates the length of time that a voyage or journey lasts from its start to its end.
-
E.
flightDuration
Indicates the length of time that a specific flight takes from departure to arrival.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.