Triple
T20939861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska Panhandle and eastern Nebraska region |
E515688
|
entity |
| Predicate | easternPartIs |
P41303
|
FINISHED |
| Object | eastern Nebraska |
—
|
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: eastern Nebraska | Statement: [Nebraska Panhandle and eastern Nebraska region, easternPartIs, eastern Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternPartIs Context triple: [Nebraska Panhandle and eastern Nebraska region, easternPartIs, eastern Nebraska]
-
A.
locatedInEasternPartOf
chosen
Indicates that one entity is situated within the eastern portion or region of another entity.
-
B.
easternPartOccupiedBy
Indicates that the eastern portion of a region, area, or object is taken up, inhabited, or used by a specified entity.
-
C.
easternmostPartOf
Indicates that one entity is the geographically furthest-east portion or segment of another entity.
-
D.
isInWesternPartOf
Indicates that one entity is located within the western part or region of another entity.
-
E.
easternProvince
Indicates that one region or administrative unit is located to the east of another within the same broader territory or country.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f954e44481909098a0b23a687d5e |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.