Triple
T3073280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgetown Pike |
E64075
|
entity |
| Predicate | westernTerminusLocation |
P4246
|
FINISHED |
| Object | near Dranesville, Virginia |
—
|
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: near Dranesville, Virginia | Statement: [Georgetown Pike, westernTerminusLocation, near Dranesville, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernTerminusLocation Context triple: [Georgetown Pike, westernTerminusLocation, near Dranesville, Virginia]
-
A.
westernTerminusNear
chosen
Indicates that the western endpoint of one entity is located close to another entity.
-
B.
westernTerminusDetail
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
C.
westernTerminusState
Indicates the state in which something (such as a route, line, or path) has its western endpoint or terminus.
-
D.
locatedWestOf
Indicates that one entity is positioned geographically to the west of another entity.
-
E.
isWesternmostPartOf
Indicates that one entity is the furthest to the west within the geographic extent or boundary of another entity.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14e372c81908c25c7f3e7e0c864 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.