Triple
T24232988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Great Plains tallgrass prairie |
E601788
|
entity |
| Predicate | historicalFauna |
P950
|
FINISHED |
| Object | American bison |
—
|
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: American bison | Statement: [Central Great Plains tallgrass prairie, historicalFauna, American bison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalFauna Context triple: [Central Great Plains tallgrass prairie, historicalFauna, American bison]
-
A.
faunaOrigin
Indicates the place or source from which an animal species or population originates.
-
B.
fauna
chosen
Indicates that an entity is an animal or part of the animal life associated with a particular place or context.
-
C.
historicalHabitat
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
D.
faunaDiversity
Indicates the variety and richness of animal species present within a given area or ecosystem.
-
E.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
- 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.