Triple
T32438242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brookfield, Vermont |
E828939
|
entity |
| Predicate | hasUnpavedStateHighway |
P141314
|
FINISHED |
| Object | Vermont Route 65 |
—
|
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: Vermont Route 65 | Statement: [Brookfield, Vermont, hasUnpavedStateHighway, Vermont Route 65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnpavedStateHighway Context triple: [Brookfield, Vermont, hasUnpavedStateHighway, Vermont Route 65]
-
A.
hasPavementStatus
chosen
Indicates the type or condition of pavement associated with an entity, such as whether a surface is paved, unpaved, or its current pavement state.
-
B.
isPavedMostOfWay
Indicates that a route or path is surfaced with pavement for the majority of its length, though not necessarily entirely.
-
C.
isPrimaryStateHighway
Indicates that a given road segment is designated as a primary (major) state highway within a state’s road network.
-
D.
containsStateHighway
Indicates that a geographic area or region includes within its boundaries at least one designated state highway.
-
E.
isRuralHighway
Indicates that a given highway is classified as being located in or primarily serving a rural area.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:55 a.m.