Triple
T29243111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennisetum glaucum |
E741362
|
entity |
| Predicate | roleInFarmingSystem |
P67954
|
FINISHED |
| Object | dryland agriculture |
—
|
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: dryland agriculture | Statement: [Pennisetum glaucum, roleInFarmingSystem, dryland agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFarmingSystem Context triple: [Pennisetum glaucum, roleInFarmingSystem, dryland agriculture]
-
A.
agriculturalRole
Indicates a role or function that an entity has within agricultural activities, production, or systems.
-
B.
farmSystemRole
chosen
Indicates the specific function, responsibility, or position an entity holds within an agricultural or farm management system.
-
C.
roleInFlock
Indicates the specific function or position an individual holds within a flock.
-
D.
servesAsFarmSystemFor
Indicates that one entity functions as a developmental or feeder system that supplies trained or prepared resources (such as players, talent, or products) to another entity.
-
E.
roleInPikmin
Indicates the specific function or part an entity plays within the context of the Pikmin series (such as a character’s or object’s role in the game).
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 28, 2026, 12:31 p.m.