Triple
T31744786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover–Calais |
E810238
|
entity |
| Predicate | typicalCrossingTime |
P22182
|
FINISHED |
| Object | about 90 minutes |
—
|
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 90 minutes | Statement: [Dover–Calais, typicalCrossingTime, about 90 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCrossingTime Context triple: [Dover–Calais, typicalCrossingTime, about 90 minutes]
-
A.
approximateCrossingTime
chosen
Indicates an estimated point in time when one entity is expected to cross or intersect another (such as a path, boundary, or trajectory).
-
B.
firstChannelCrossingTime
Indicates the time at which an entity first crosses a specified channel or boundary.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
E.
typicalSettlementTime
Indicates the usual or expected amount of time it takes for a transaction or obligation to be fully settled.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:26 p.m.