Triple
T29672643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schizachyrium scoparium |
E750715
|
entity |
| Predicate | erosionControl |
P59815
|
FINISHED |
| Object | used for soil stabilization |
—
|
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: used for soil stabilization | Statement: [Schizachyrium scoparium, erosionControl, used for soil stabilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionControl Context triple: [Schizachyrium scoparium, erosionControl, used for soil stabilization]
-
A.
erosionResistance
Indicates how strongly one entity can withstand or prevent being worn away, degraded, or removed by erosive forces caused by another entity or the environment.
-
B.
erosionAgent
Indicates the natural force or process responsible for wearing away, transporting, or reshaping material from a surface.
-
C.
erosionRate
Indicates the rate at which material is worn away or removed from a surface over time due to erosive processes.
-
D.
erosionConcern
Indicates concern that a location, structure, or resource is being or may be negatively affected by erosion.
-
E.
designedForSedimentControl
chosen
Indicates that something is specifically created or configured to manage, reduce, or control the movement and accumulation of sediment.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672598730819093b766fd418e1c08 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:05 p.m.