Triple
T7422439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky bluegrass |
E171281
|
entity |
| Predicate | forageQuality |
P76873
|
FINISHED |
| Object | high-quality pasture forage for livestock |
—
|
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: high-quality pasture forage for livestock | Statement: [Kentucky bluegrass, forageQuality, high-quality pasture forage for livestock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forageQuality Context triple: [Kentucky bluegrass, forageQuality, high-quality pasture forage for livestock]
-
A.
foragingStratum
Indicates the vertical layer or height within a habitat where an organism typically searches for and obtains its food.
-
B.
foragingStrategy
Indicates the method or pattern an organism uses to search for, obtain, and exploit food resources.
-
C.
foragingZone
Indicates the area or region where an entity typically searches for and collects food.
-
D.
meatQuality
Indicates the assessed level or characteristics of quality associated with a given piece or type of meat.
-
E.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
- F. None of above. chosen
Provenance (4 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ed29ec8190804564185fe20797 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:11 p.m.