Triple
T7007072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darke County, Ohio |
E162482
|
entity |
| Predicate | gnisFeatureClass |
P9677
|
FINISHED |
| Object | civil |
—
|
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: civil | Statement: [Darke County, Ohio, gnisFeatureClass, civil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gnisFeatureClass Context triple: [Darke County, Ohio, gnisFeatureClass, civil]
-
A.
GNISFeatureClass
chosen
Indicates the categorical type or class assigned to a geographic feature in the Geographic Names Information System (GNIS).
-
B.
USGSFeatureClass
Indicates a classification relationship where a geographic feature is assigned a specific feature class category as defined by the U.S. Geological Survey.
-
C.
GNISFeatureID
Indicates that an entity is associated with a specific identifier assigned by the U.S. Geological Survey’s Geographic Names Information System (GNIS) to uniquely reference a geographic feature.
-
D.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
E.
eraClassification
Indicates the historical era or time period into which an entity is categorized or classified.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc35cb848190a839919021efce81 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.