Triple
T2719681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupinus angustifolius |
E60051
|
entity |
| Predicate | seedComposition |
P41842
|
FINISHED |
| Object | high protein |
—
|
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 protein | Statement: [Lupinus angustifolius, seedComposition, high protein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seedComposition Context triple: [Lupinus angustifolius, seedComposition, high protein]
-
A.
standardComposition
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
B.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
C.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
D.
seedSize
Indicates the relative magnitude or dimensions of a seed in comparison to others or to a standard.
-
E.
seedUse
Indicates the use or application of seeds for a particular purpose, such as planting, cultivation, or propagation.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab06d388190acf690787fe58ab5 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:55 p.m.