Triple
T1489406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West End station |
E29541
|
entity |
| Predicate | hasConnections |
P8776
|
FINISHED |
| Object | DART bus routes |
—
|
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: DART bus routes | Statement: [West End station, hasConnections, DART bus routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnections Context triple: [West End station, hasConnections, DART bus routes]
-
A.
hasTeleconnectionsWith
Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
-
B.
hasConnection
chosen
Indicates that there exists a link, association, or relationship between two entities.
-
C.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a6095481909e9d406ac9a41828 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.