Triple
T1804944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza glaberrima |
E40199
|
entity |
| Predicate | yieldRelativeToOryza sativa |
P32571
|
FINISHED |
| Object | generally lower |
—
|
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: generally lower | Statement: [Oryza glaberrima, yieldRelativeToOryza sativa, generally lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yieldRelativeToOryza sativa Context triple: [Oryza glaberrima, yieldRelativeToOryza sativa, generally lower]
-
A.
numberOfRiceStalks
Indicates the quantity or count of rice stalks associated with a given entity or context.
-
B.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
C.
grain
Indicates that one entity is composed of or contains a granular substance or small particles of another entity.
-
D.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
-
E.
isExportOrientedCultivar
Indicates that a cultivar is primarily developed, selected, or used for production aimed at export markets rather than domestic consumption.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d514c081908197ac1f7c7d7a88 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba67554788190b429f2b9f0a70310 |
completed | March 7, 2026, 4:15 a.m. |
Created at: March 4, 2026, 7:32 p.m.