Triple
T1804873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IR36 |
E40197
|
entity |
| Predicate | grainQuality |
P6861
|
FINISHED |
| Object | intermediate amylose content |
—
|
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: intermediate amylose content | Statement: [IR36, grainQuality, intermediate amylose content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grainQuality Context triple: [IR36, grainQuality, intermediate amylose content]
-
A.
grain
Indicates that one entity is composed of or contains a granular substance or small particles of another entity.
-
B.
fieldQuality
Indicates the assessed level or degree of quality associated with a particular field or attribute in a given context.
-
C.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
-
D.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
E.
quality
chosen
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
- 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_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. |
Created at: March 4, 2026, 7:32 p.m.