Triple
T25408374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 16 (New Brunswick) |
E636619
|
entity |
| Predicate | terminusTowards |
P159755
|
FINISHED |
| Object | Confederation Bridge |
—
|
NE NERFINISHED |
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: Confederation Bridge | Statement: [Route 16 (New Brunswick), terminusTowards, Confederation Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusTowards Context triple: [Route 16 (New Brunswick), terminusTowards, Confederation Bridge]
-
A.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
B.
terminusFrom
Indicates that something serves as the endpoint or final destination from which a route, path, or connection originates.
-
C.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
D.
terminusUpper
Indicates that one entity serves as the upper or final endpoint (terminus) of another entity, such as a route, segment, or ordered structure.
-
E.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
- F. None of above. chosen
Provenance (4 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 1:52 p.m.