Triple
T20800414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS Chi-Cheemaun |
E512022
|
entity |
| Predicate | crossingTime |
P22182
|
FINISHED |
| Object | approximately 1 hour 45 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: approximately 1 hour 45 minutes | Statement: [MS Chi-Cheemaun, crossingTime, approximately 1 hour 45 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossingTime Context triple: [MS Chi-Cheemaun, crossingTime, approximately 1 hour 45 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.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
crossingDate
Indicates the date on which the crossing event between the related entities took place.
-
D.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
E.
crossingOpened
Indicates that a crossing (such as a road, rail, or pedestrian crossing) has been opened or made available for passage.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b014648190a1133836b36c26cd |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.