Triple
T1443843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marion County |
E31132
|
entity |
| Predicate | gnisId |
P228
|
FINISHED |
| Object | 0452528 |
—
|
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: 0452528 | Statement: [Marion County, gnisId, 0452528]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gnisId Context triple: [Marion County, gnisId, 0452528]
-
A.
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.
-
B.
GNISID
chosen
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
-
C.
GNISFeatureClass
Indicates the categorical type or class assigned to a geographic feature in the Geographic Names Information System (GNIS).
-
D.
hasNationalParkServiceUnitCode
Indicates that an entity is associated with a specific National Park Service unit, identified by its official unit code.
-
E.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.