Triple
T16864542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of Orchy |
E410004
|
entity |
| Predicate | hasRailCode |
P18202
|
FINISHED |
| Object | BRO |
E636441
|
NE 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: BRO | Statement: [Bridge of Orchy, hasRailCode, BRO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRO Context triple: [Bridge of Orchy, hasRailCode, BRO]
-
A.
BRO
BRO is the Border Roads Organisation, an Indian government agency responsible for constructing and maintaining roads and infrastructure in border and strategic areas.
-
B.
BRO
chosen
BRO is the National Rail station code for Broxbourne railway station in Hertfordshire, England.
-
C.
BRO
BRO is the IATA airport code for Brownsville South Padre Island International Airport, a commercial airport serving Brownsville and the South Padre Island area in Texas, USA.
-
D.
The Bro
The Bro is a high-thrill water slide attraction at WhiteWater World, known for its fast, twisting ride experience.
-
E.
Bro
Bro is a locality in Stockholm County, Sweden, known as one of the main population centers within Upplands-Bro Municipality.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b505a390819097ec31cd210eca60 |
completed | April 18, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb294c0481908306e1f604cc7404 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.