Triple
T32493830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Midwest of the United States |
E830462
|
entity |
| Predicate | oftenIncludesState |
P11085
|
FINISHED |
| Object | Iowa |
—
|
NE NERFINISHED |
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: Iowa | Statement: [Upper Midwest of the United States, oftenIncludesState, Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenIncludesState Context triple: [Upper Midwest of the United States, oftenIncludesState, Iowa]
-
A.
includesMostOfState
Indicates that one geographic or political entity contains the majority of the area or extent of a given state within its boundaries.
-
B.
stateIncludes
Indicates that a given state encompasses, contains, or has within its boundaries another specified entity or region.
-
C.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
D.
includesStateOrProvince
chosen
Indicates that one entity geographically contains or encompasses a specific state or province within its boundaries.
-
E.
servesPartOfState
Indicates that an entity serves as an official or functional part of a larger state-level governmental or administrative structure.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 12:59 a.m.