Triple
T24973887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation in Montgomery County, Maryland |
E624963
|
entity |
| Predicate | hasMetroStationArea |
P158757
|
FINISHED |
| Object | Rockville |
—
|
NE NERFINISHED |
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: Rockville | Statement: [Transportation in Montgomery County, Maryland, hasMetroStationArea, Rockville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetroStationArea Context triple: [Transportation in Montgomery County, Maryland, hasMetroStationArea, Rockville]
-
A.
hasMetroStations
Indicates that a place or area is served by one or more metro (subway) stations.
-
B.
hasMetroTerminus
Indicates that one location serves as the terminal (end) station of a metro line for another location.
-
C.
nearMetroStation
Indicates that one entity is located close to or within a short walking distance of a metro (subway) station.
-
D.
isWithinMetroArea
Indicates that one location lies inside the geographic boundaries of a specified metropolitan area.
-
E.
hasStationDistrict
Indicates that a station is located within or associated with a particular administrative district.
- F. None of above. chosen
Provenance (4 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 6:01 a.m.