Triple
T12077145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courthouse |
E287579
|
entity |
| Predicate | servedBy |
P82
|
FINISHED |
| Object | Courthouse station |
E623985
|
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: Courthouse station | Statement: [Courthouse, servedBy, Courthouse station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Courthouse station Context triple: [Courthouse, servedBy, Courthouse station]
-
A.
Courthouse station
chosen
Courthouse station is an underground MBTA Silver Line bus rapid transit station serving Boston's Seaport District.
-
B.
Courthouse station
Courthouse station is a light rail station in downtown Salt Lake City, Utah, serving the Utah Transit Authority’s TRAX system.
-
C.
Court House station
Court House station is a Washington Metro rapid transit station serving the Courthouse neighborhood in Arlington, Virginia.
-
D.
Briarwood station
Briarwood station is a New York City Subway station in Queens serving the IND Queens Boulevard Line.
-
E.
Edgewood station
Edgewood station is a commuter rail stop in Edgewood, Maryland, served by MARC’s Penn Line between Baltimore and Perryville.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9045ceeec81909427cae8972eed26 |
completed | April 10, 2026, 2:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f660f48881908d50bf27b0892953 |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.