Triple
T20556678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacoma Link light rail |
E504736
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | T Line |
—
|
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: T Line | Statement: [Tacoma Link light rail, alsoKnownAs, T Line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: T Line Context triple: [Tacoma Link light rail, alsoKnownAs, T Line]
-
A.
T Line
chosen
The T Line is a streetcar-style light rail route within the Sound Transit Link system serving Tacoma, Washington.
-
B.
S Line
The S Line is a route within the Sounder commuter rail system that provides passenger rail service in the Seattle metropolitan area.
-
C.
S Line
The S Line is a modern streetcar route in the Salt Lake City area that provides local transit service and links neighborhoods to the broader TRAX light rail network.
-
D.
N Line
The N Line is a Sounder commuter rail route serving communities north of Seattle in Washington State.
-
E.
N Line
The N Line is a New York City Subway service that runs through Brooklyn and other boroughs, connecting neighborhoods in southern Brooklyn to Manhattan and Queens.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5de9c008190b8620628fb285e90 |
completed | April 20, 2026, 10:17 p.m. |
Created at: April 16, 2026, 11:38 a.m.