Triple
T36279315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York City Region |
E892893
|
entity |
| Predicate | linkedByTransportRoute |
P132153
|
FINISHED |
| Object | A64 road |
—
|
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: A64 road | Statement: [York City Region, linkedByTransportRoute, A64 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedByTransportRoute Context triple: [York City Region, linkedByTransportRoute, A64 road]
-
A.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
B.
transportationRelation
Indicates a relationship where one entity transports, carries, or conveys another entity from one location to another.
-
C.
isTransportationLinkBetween
chosen
Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two entities.
-
D.
associatedWithTransitLine
Indicates that an entity has a connection or linkage to a specific transit line, such as being part of, served by, or otherwise related to that line.
-
E.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:09 p.m.