Triple
T3073304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgetown Pike |
E64075
|
entity |
| Predicate | hasHeritageStatus |
P923
|
FINISHED |
| Object | listed as a historic road corridor by Virginia authorities |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: listed as a historic road corridor by Virginia authorities | Statement: [Georgetown Pike, hasHeritageStatus, listed as a historic road corridor by Virginia authorities]
Provenance (2 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. |
Created at: March 8, 2026, 3:02 p.m.