Triple
T28283587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirby, Vermont |
E713217
|
entity |
| Predicate | isInCaledoniaCounty |
P23957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kirby, Vermont, isInCaledoniaCounty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCaledoniaCounty Context triple: [Kirby, Vermont, isInCaledoniaCounty, true]
-
A.
isInCadastralCounty
Indicates that one entity is located within, and administratively belongs to, a specific cadastral county used for land and property registration.
-
B.
isInJacksonCountySeatRegion
Indicates that one entity is located within the designated county seat region of Jackson County.
-
C.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
D.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
E.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:24 p.m.