Triple
T13664909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | central Vermont |
E327090
|
entity |
| Predicate | positionWithinState |
P69120
|
FINISHED |
| Object | central part of 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: central part of Vermont | Statement: [central Vermont, positionWithinState, central part of Vermont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinState Context triple: [central Vermont, positionWithinState, central part of Vermont]
-
A.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
B.
statePosition
Indicates the spatial or situational position or status of an entity within a defined context or system.
-
C.
regionalLocationWithinState
chosen
Indicates that one region is geographically located within the boundaries of a specific state.
-
D.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
E.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc622a07c81909ef7fb55e719dd9a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.