Triple
T4201173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maynardville |
E86067
|
entity |
| Predicate | isInCountySeatRoleSince |
P26682
|
FINISHED |
| Object | 1850 |
—
|
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: 1850 | Statement: [Maynardville, isInCountySeatRoleSince, 1850]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCountySeatRoleSince Context triple: [Maynardville, isInCountySeatRoleSince, 1850]
-
A.
hasCountySeatWithRole
Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
-
B.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
C.
countySeatSince
chosen
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
-
D.
hasCountySeatFunction
Indicates that an entity serves as the official county seat, functioning as the administrative center for a county.
-
E.
hasCountySeatRelation
Indicates that a specific place serves as the county seat (administrative center) of a particular 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af037da30481908106b27a88d59140 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.