Triple
T30102150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia State Route 227 |
E765025
|
entity |
| Predicate | terminusServes |
P388
|
FINISHED |
| Object | Urbanna central business district |
—
|
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: Urbanna central business district | Statement: [Virginia State Route 227, terminusServes, Urbanna central business district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusServes Context triple: [Virginia State Route 227, terminusServes, Urbanna central business district]
-
A.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
B.
terminusConnectsTo
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
-
C.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
D.
terminusCoastal
Indicates that the endpoint or terminus of something (e.g., a route, line, or feature) is located on or directly adjacent to a coast.
-
E.
terminusDescription
Indicates the textual description that characterizes the endpoint or final stop of a route, path, or process.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 7:08 p.m.