Triple
T8306369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husky Stadium |
E194472
|
entity |
| Predicate | accessibleBy |
P1017
|
FINISHED |
| Object | Link light rail |
E53254
|
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: Link light rail | Statement: [Husky Stadium, accessibleBy, Link light rail]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Link light rail Context triple: [Husky Stadium, accessibleBy, Link light rail]
-
A.
Link light rail
chosen
Link light rail is a regional light rail transit system serving the Seattle metropolitan area in Washington State, operated by Sound Transit.
-
B.
Light RailLink
Light RailLink is a light rail transit system in the Baltimore metropolitan area that provides north–south rail service through the city and its suburbs.
-
C.
METRO light rail
METRO light rail is a rapid transit system serving the Minneapolis–Saint Paul metropolitan area with multiple color-designated lines connecting key urban, suburban, and airport destinations.
-
D.
MAX Light Rail
MAX Light Rail is the metropolitan light rail transit system serving the Portland, Oregon, metropolitan area.
-
E.
METRORail light rail
METRORail light rail is Houston's urban light rail transit system operated by METRO, connecting key destinations throughout the city’s central area.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd955100448190862fd52d660585fd |
completed | April 1, 2026, 9:59 p.m. |
Created at: March 30, 2026, 5:54 p.m.