Triple
T18817381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheshire Ring |
E460171
|
entity |
| Predicate | approximateDurationByBoat |
P109944
|
FINISHED |
| Object | one to two 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: one to two weeks | Statement: [Cheshire Ring, approximateDurationByBoat, one to two weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDurationByBoat Context triple: [Cheshire Ring, approximateDurationByBoat, one to two weeks]
-
A.
voyageDuration
Indicates the length of time that a voyage or journey lasts from its start to its end.
-
B.
approximateTripDuration
chosen
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
-
C.
travelTimeByFerry
Indicates the duration required to travel between two locations specifically using a ferry as the mode of transportation.
-
D.
vesselEndurance
Indicates the duration or capacity of a vessel to operate or remain functional under specified conditions before requiring resupply, maintenance, or rest.
-
E.
numberOfBoatsWidth
Indicates the count of boats arranged or present across the width of a given area or span.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b620248190afa21a6ce61e2cff |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.