Triple
T11548957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumex |
E273841
|
entity |
| Predicate | edibleUse |
P23620
|
FINISHED |
| Object | leaves used as leafy vegetable in some cuisines |
—
|
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: leaves used as leafy vegetable in some cuisines | Statement: [Rumex, edibleUse, leaves used as leafy vegetable in some cuisines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edibleUse Context triple: [Rumex, edibleUse, leaves used as leafy vegetable in some cuisines]
-
A.
culinaryUse
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
-
B.
edibleSpecies
Indicates that one species can be safely eaten as food by another species or by humans.
-
C.
usedAsFood
Indicates that one entity is consumed or intended to be consumed as food by another entity.
-
D.
ediblePart
chosen
Indicates that one entity is a part of another entity that can be eaten or consumed.
-
E.
usesIngredient
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.