Triple
T14295960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethesda Metro station |
E354437
|
entity |
| Predicate | oneOfDeepestStationsInSystem |
P84282
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bethesda Metro station, oneOfDeepestStationsInSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfDeepestStationsInSystem Context triple: [Bethesda Metro station, oneOfDeepestStationsInSystem, yes]
-
A.
oneOfDeepestStationsIn
chosen
Indicates that a station is among the deepest stations located within a specified area or system.
-
B.
deepestStation
Indicates that one station in a network or system is located at a greater depth (e.g., below ground or sea level) than all other stations.
-
C.
deepestStationDepthMeters
Indicates the maximum depth, in meters, reached by any station associated with the subject.
-
D.
oneOfDeepestPointsOn
Indicates that an entity is among the deepest points located on a specified object or surface.
-
E.
isEasternmostSubwayStationOn
Indicates that a subway station is the geographically farthest east station located on a given subway line.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717b35ec81908968994e65737c66 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.