Triple
T11422859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadium Station |
E270668
|
entity |
| Predicate | partOfLine |
P6309
|
FINISHED |
| Object | Central Link |
E266736
|
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: Central Link | Statement: [Stadium Station, partOfLine, Central Link]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Central Link Context triple: [Stadium Station, partOfLine, Central Link]
-
A.
Central Link
chosen
Central Link was the original name for Seattle’s first light rail line, now part of the city’s Link light rail system.
-
B.
The Link
The Link is a key University College Birmingham facility that provides modern teaching, learning, and student support spaces.
-
C.
Triangle Link
Triangle Link is a major fixed-link bridge and tunnel system in western Norway that connects the islands of Bømlo and Stord to the mainland.
-
D.
Sun Link
Sun Link is a modern streetcar system serving downtown Tucson, Arizona, and nearby districts as part of the city’s public transit network.
-
E.
NovaLink
NovaLink is an IBM Power Systems virtualization management interface that streamlines the deployment and control of virtual machines and resources on Power hardware.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b8a1e88c8190994bea88a0490e60 |
completed | April 20, 2026, 5:24 a.m. |
Created at: April 8, 2026, 9:34 p.m.