Triple
T3058822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross Timbers |
E60545
|
entity |
| Predicate | dominantGrassSpecies |
P38050
|
FINISHED |
| Object | little bluestem |
—
|
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: little bluestem | Statement: [Cross Timbers, dominantGrassSpecies, little bluestem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantGrassSpecies Context triple: [Cross Timbers, dominantGrassSpecies, little bluestem]
-
A.
hasDominantSpecies
chosen
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
B.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
C.
dominantEnvironment
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
-
D.
dominantTree
Indicates that one tree has a dominant or prevailing influence over another tree, such as in size, canopy coverage, or competitive advantage within a shared environment.
-
E.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e1741648190b710b7022252498d |
completed | March 8, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.