Triple
T23691752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A705 |
E585319
|
entity |
| Predicate | providesTransportLinkTo |
P93339
|
FINISHED |
| Object | Howden |
—
|
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: Howden | Statement: [A705, providesTransportLinkTo, Howden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesTransportLinkTo Context triple: [A705, providesTransportLinkTo, Howden]
-
A.
transportLinkType
Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
-
B.
transportationLinksTo
chosen
Indicates that there is a transportation connection or route enabling movement or travel between the two entities.
-
C.
hasGoodTransportLinks
Indicates that a place is well connected to other locations by efficient and convenient transport options.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
transportDependency
Indicates that one entity’s ability to be transported or to function in transport depends on another entity or transport resource.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c27af481908c6dbe59c71de82a |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.