Triple
T1337288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hancock, Iowa |
E28781
|
entity |
| Predicate | FIPSStateCode |
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: [Hancock, Iowa, FIPSStateCode, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIPSStateCode Context triple: [Hancock, Iowa, FIPSStateCode, 19]
-
A.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
stateSubdivisionCode
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
C.
keyUSState
Indicates that a U.S. state plays a primary or strategically important role in a given context (such as politics, economy, or policy).
-
D.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
E.
majorReceivingState
Indicates that an entity serves as the primary or principal recipient in a given relationship, transaction, or flow.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1edda1c81909a1149b254b0d57e |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.