Triple
T35131453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell County–Charlotte County line |
E1014445
|
entity |
| Predicate | hasSubdivisionTypeOnEachSide |
P36805
|
FINISHED |
| Object | county |
—
|
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: county | Statement: [Campbell County–Charlotte County line, hasSubdivisionTypeOnEachSide, county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubdivisionTypeOnEachSide Context triple: [Campbell County–Charlotte County line, hasSubdivisionTypeOnEachSide, county]
-
A.
hasBorderingSubdivision
Indicates that one subdivision directly borders or shares a boundary with another subdivision.
-
B.
hasTypeOfSubdivision
chosen
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
C.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
D.
hasSubdivisionTypical
Indicates that an entity typically has a particular kind of subdivision as a characteristic or representative part of its structure.
-
E.
subdivisionFlagOf
Indicates that one administrative or territorial unit is a designated subdivision or sub-part of another unit.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:02 p.m.