Triple
T24233016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Great Plains tallgrass prairie |
E601788
|
entity |
| Predicate | historicalBisonHerds |
P130010
|
FINISHED |
| Object | extensive |
—
|
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: extensive | Statement: [Central Great Plains tallgrass prairie, historicalBisonHerds, extensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalBisonHerds Context triple: [Central Great Plains tallgrass prairie, historicalBisonHerds, extensive]
-
A.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
B.
historicallyNomadic
Indicates that an entity has traditionally led a mobile, wandering lifestyle without permanent settlement over a significant historical period.
-
C.
historicalHabitat
chosen
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
D.
historicalFrontier
Indicates a boundary or border that historically separated two regions, territories, or spheres of influence.
-
E.
hasBighornSheep
Indicates that the subject possesses, contains, or is associated with one or more bighorn sheep.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a98a6a4819085ab955654fa444f |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.