Triple
T2830962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stowe |
E62233
|
entity |
| Predicate | locatedInPartOfState |
P31574
|
FINISHED |
| Object | northern Vermont |
—
|
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: northern Vermont | Statement: [Stowe, locatedInPartOfState, northern Vermont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPartOfState Context triple: [Stowe, locatedInPartOfState, northern Vermont]
-
A.
locatedInFormerState
Indicates that an entity is or was geographically situated within the boundaries of a political state that no longer exists in its former form.
-
B.
locatedInFederalEntity
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
C.
locatedInModernState
Indicates that one entity is geographically situated within the boundaries of a specified contemporary nation-state.
-
D.
isInUSState
chosen
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
E.
tookPlaceInState
Indicates that an event or occurrence happened within the geographical or political boundaries of a specific state.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebd5a2c81908f0e30a0ae0eb8df |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.