Triple
T11263852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 520 |
E266630
|
entity |
| Predicate | hasNearbyAccess |
P98808
|
FINISHED |
| Object | Bellevue |
E654633
|
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: Bellevue | Statement: [State Route 520, hasNearbyAccess, Bellevue]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bellevue Context triple: [State Route 520, hasNearbyAccess, Bellevue]
-
A.
Bellevue
Bellevue is a small municipality located along Lake Geneva in the canton of Geneva in southwestern Switzerland.
-
B.
Bellevue
Bellevue is a scenic mountain station in the French Alps that serves as a popular starting point for hikes and ascents around Mont Blanc.
-
C.
Bellevue
chosen
Bellevue is a city in eastern Nebraska, part of the Omaha metropolitan area and one of the state's oldest continuous settlements.
-
D.
Bellevue
Bellevue is a commuter rail station in West Roxbury, Boston, served by the MBTA's Needham Line.
-
E.
Bellevue
Bellevue is a residential suburb of Johannesburg, South Africa, known for its dense urban character and proximity to the inner-city neighborhoods of Yeoville and Berea.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94d56048190bf808e1bc2188714 |
completed | April 9, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef81c65ba48190a8e2b9d7078cd978 |
completed | April 27, 2026, 3:33 p.m. |
Created at: April 8, 2026, 9:31 p.m.