Triple
T8041033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheltenham Avenue (north end) |
E187438
|
entity |
| Predicate | directionOfEndpoint |
P34413
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Cheltenham Avenue (north end), directionOfEndpoint, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfEndpoint Context triple: [Cheltenham Avenue (north end), directionOfEndpoint, north]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
terminusDirection
chosen
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
E.
directionalDesignation
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1d62c48190bf4a6cd17517c5dc |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.