Triple
T24814451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Highway 622 |
E620875
|
entity |
| Predicate | terminusBConnection |
P50561
|
FINISHED |
| Object | Ontario Highway 17 |
—
|
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: Ontario Highway 17 | Statement: [Ontario Highway 622, terminusBConnection, Ontario Highway 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusBConnection Context triple: [Ontario Highway 622, terminusBConnection, Ontario Highway 17]
-
A.
terminusWestConnection
Indicates that one entity serves as the western endpoint where it connects to another entity or route.
-
B.
terminusBState
Indicates the state or condition of the entity that serves as the endpoint (B terminus) of a connection, process, or relationship.
-
C.
terminusSouthConnection
Indicates a connection where one entity serves as the southern terminus or endpoint of another entity.
-
D.
terminusJunction
chosen
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
-
E.
terminusPort
Indicates the port at which a route, journey, or connection ends or terminates.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:01 a.m.