Triple
T1954163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlottesville western bypass corridor |
E42226
|
entity |
| Predicate | intendedToServe |
P33500
|
FINISHED |
| Object | U.S. Route 29 |
—
|
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: U.S. Route 29 | Statement: [Charlottesville western bypass corridor, intendedToServe, U.S. Route 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedToServe Context triple: [Charlottesville western bypass corridor, intendedToServe, U.S. Route 29]
-
A.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
B.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
-
C.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
D.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
E.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb351c148819080173c09876e814a |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1ddccbc8190bf2bd8bac673c0c5 |
completed | March 7, 2026, 5:04 a.m. |
Created at: March 4, 2026, 7:36 p.m.