Triple
T34046673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restless legs syndrome |
E873102
|
entity |
| Predicate | hasAssociatedNutrient |
P190380
|
FINISHED |
| Object | iron |
—
|
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: iron | Statement: [Restless legs syndrome, hasAssociatedNutrient, iron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedNutrient Context triple: [Restless legs syndrome, hasAssociatedNutrient, iron]
-
A.
hasNutrientContent
Indicates that one entity contains or provides a specified amount or type of nutrient relative to another entity or standard.
-
B.
hasNutrientStatus
Indicates that an entity possesses a particular nutritional condition or level, such as being deficient, sufficient, or excessive in specific nutrients.
-
C.
hasKeyNutrientRole
Indicates that something plays an essential or primary role as a nutrient in supporting a biological function or process.
-
D.
hasNutritionalConcern
Indicates that an entity is associated with a specific nutritional issue, risk, or dietary concern.
-
E.
isEssentialNutrientFor
Indicates that one entity is a nutrient required for the normal growth, function, or survival of another entity.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:51 a.m.