Triple
T28589475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barre–Montpelier micropolitan area |
E723601
|
entity |
| Predicate | includesStateCapital |
P67825
|
FINISHED |
| Object | Montpelier, Vermont |
—
|
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: Montpelier, Vermont | Statement: [Barre–Montpelier micropolitan area, includesStateCapital, Montpelier, Vermont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesStateCapital Context triple: [Barre–Montpelier micropolitan area, includesStateCapital, Montpelier, Vermont]
-
A.
isStateCapital
Indicates that a city serves as the official capital of a given state.
-
B.
stateCapitalStatus
Indicates that an entity serves as the official capital city of a specified state or state-level administrative region.
-
C.
hasCapitalOfContainingState
chosen
Indicates that a capital city is the official capital of a state that geographically contains a given area or entity.
-
D.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
E.
hasBorderingStateCapital
Indicates that one state capital city is directly adjacent to or shares a border with another state capital city.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 28, 2026, 4:19 a.m.