Triple
T1804966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza glaberrima |
E40199
|
entity |
| Predicate | comparisonWithAsianRice |
P32574
|
FINISHED |
| Object | more resilient to local stresses |
—
|
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: more resilient to local stresses | Statement: [Oryza glaberrima, comparisonWithAsianRice, more resilient to local stresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparisonWithAsianRice Context triple: [Oryza glaberrima, comparisonWithAsianRice, more resilient to local stresses]
-
A.
numberOfRiceStalks
Indicates the quantity or count of rice stalks associated with a given entity or context.
-
B.
grain
Indicates that one entity is composed of or contains a granular substance or small particles of another entity.
-
C.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
D.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
E.
rankByLengthInAsia
Indicates that entities are ordered or compared based on their length within the context of Asia.
- 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.