Triple
T13839996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maysville Road veto |
E332631
|
entity |
| Predicate | appliesToProjectType |
P12865
|
FINISHED |
| Object | turnpike road |
—
|
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: turnpike road | Statement: [Maysville Road veto, appliesToProjectType, turnpike road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToProjectType Context triple: [Maysville Road veto, appliesToProjectType, turnpike road]
-
A.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
B.
hasProjectType
chosen
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
C.
appliesToReleaseType
Indicates that a rule, condition, or attribute is specifically relevant or restricted to a particular type of release.
-
D.
eligibleProjectType
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
E.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ae5e4c8190ad85ad2968bc71b2 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.