Triple
T3893643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far North Line |
E88118
|
entity |
| Predicate | endpointDirection |
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: [Far North Line, endpointDirection, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointDirection Context triple: [Far North Line, endpointDirection, north]
-
A.
terminusDirection
chosen
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
B.
serviceDirection
Indicates the direction or orientation in which a service is provided or operates relative to involved entities.
-
C.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
netTransportDirection
Indicates the overall direction in which something (such as material, energy, or information) is being transported when considering all contributing flows together.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.