Triple
T2614200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basellaceae |
E58847
|
entity |
| Predicate | edibility |
P25824
|
FINISHED |
| Object | several species cultivated as vegetables |
—
|
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: several species cultivated as vegetables | Statement: [Basellaceae, edibility, several species cultivated as vegetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edibility Context triple: [Basellaceae, edibility, several species cultivated as vegetables]
-
A.
ediblePart
Indicates that one entity is a part of another entity that can be eaten or consumed.
-
B.
culinaryUse
chosen
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
-
C.
containsEdiblePlant
Indicates that one entity includes within it, or has as part of its contents, a plant or plant part that is suitable for consumption as food.
-
D.
isCarnivorous
Indicates that an entity feeds primarily or exclusively on other animals.
-
E.
mayBeGivenTo
Indicates that something is permitted or eligible to be transferred, assigned, or provided from one entity to another.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.