Triple
T24667445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinston micropolitan area |
E610722
|
entity |
| Predicate | countySeatOfCoreCounty |
P27090
|
FINISHED |
| Object | Lenoir County, North Carolina |
—
|
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: Lenoir County, North Carolina | Statement: [Kinston micropolitan area, countySeatOfCoreCounty, Lenoir County, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countySeatOfCoreCounty Context triple: [Kinston micropolitan area, countySeatOfCoreCounty, Lenoir County, North Carolina]
-
A.
countySeat
Indicates that one place serves as the administrative center or capital of a county.
-
B.
otherCountySeat
Indicates that one entity serves as the county seat of a different county than the one associated with the other entity.
-
C.
containsCountySeat
Indicates that one administrative region or area includes within its boundaries the designated county seat location of a county.
-
D.
hasCountySeatOf
chosen
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
E.
nearestCountySeat
Indicates that one location is the closest county seat geographically to another location.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:41 a.m.