Triple
T3041346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doon, Iowa |
E83135
|
entity |
| Predicate | isInFIPSState |
P227
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Doon, Iowa, isInFIPSState, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFIPSState Context triple: [Doon, Iowa, isInFIPSState, 19]
-
A.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
C.
isStateFlagOf
Indicates that one entity is the official state flag representing the specified state or region.
-
D.
isStateSupported
Indicates that a particular state or condition is recognized, allowed, or handled within a given system or context.
-
E.
isInUnitedStatesMunicipalHierarchy
Indicates that one administrative or governmental unit occupies a specific level or position within the municipal hierarchy of the United States (e.g., city, town, county, or similar local jurisdiction).
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b5b92088190971bed04e65c5917 |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.