Triple
T23335565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska–Kansas state line |
E591570
|
entity |
| Predicate | separatesRegions |
P50632
|
FINISHED |
| Object | central Great Plains |
—
|
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: central Great Plains | Statement: [Nebraska–Kansas state line, separatesRegions, central Great Plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesRegions Context triple: [Nebraska–Kansas state line, separatesRegions, central Great Plains]
-
A.
separatedRegion
Indicates that one region is distinct from and not contiguous with another region, with a clear separation between them.
-
B.
separatedAsRegion
Indicates that one entity is distinguished or partitioned from others as a distinct region or area.
-
C.
separatesLinguisticRegions
Indicates that one entity serves as a boundary or divider between distinct linguistic regions or language areas.
-
D.
separatesTerritoryOf
Indicates that one entity serves as a boundary or divider between the territories or domains of two other entities.
-
E.
separatesState
chosen
Indicates that one entity serves as a dividing boundary or barrier between two distinct states or regions.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f08fe481908766e674164d6d45 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.