Triple
T1295188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redmond, Washington, United States |
E27637
|
entity |
| Predicate | hasPlannedTransit |
P10988
|
FINISHED |
| Object | Link light rail extension |
—
|
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: Link light rail extension | Statement: [Redmond, Washington, United States, hasPlannedTransit, Link light rail extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedTransit Context triple: [Redmond, Washington, United States, hasPlannedTransit, Link light rail extension]
-
A.
hasTransitFocus
Indicates that something is oriented toward, prioritizes, or is primarily concerned with transit or transportation services.
-
B.
hasPlan
chosen
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
C.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.