Triple
T3527799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petworth |
E74582
|
entity |
| Predicate | metroLine |
P848
|
FINISHED |
| Object | Yellow Line |
E14071
|
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: Yellow Line | Statement: [Petworth, metroLine, Yellow Line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yellow Line Context triple: [Petworth, metroLine, Yellow Line]
-
A.
Yellow Line
chosen
The Yellow Line is one of the color-coded rapid transit routes in the Washington Metro system, running primarily in a north–south direction and serving key areas in Washington, D.C. and Northern Virginia.
-
B.
Yellow Line
The Yellow Line is a rapid transit route in Chicago's 'L' system that connects the northern suburb of Skokie to the city's rail network.
-
C.
Yellow Line
The Yellow Line is one of the primary passenger rail routes of the Tyne and Wear Metro rapid transit system serving the Newcastle upon Tyne area in North East England.
-
D.
Yellow Line
The Yellow Line is one of the main lines of the Lisbon Metro system, connecting key residential and commercial areas of Portugal’s capital.
-
E.
Yellow Line
The Yellow Line is a designated route within the Baltimore Light Rail system that serves as one of its primary color-coded service lines.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc6d099c8190b2b1e65a56e52089 |
completed | March 8, 2026, 6:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4daf2b170819095a337246675e4c4 |
completed | March 14, 2026, 3:50 a.m. |
Created at: March 8, 2026, 3:19 p.m.