Triple
T2661230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta vulgaris |
E54729
|
entity |
| Predicate | isGrownFor |
P37212
|
FINISHED |
| Object | edible roots |
—
|
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: edible roots | Statement: [Beta vulgaris, isGrownFor, edible roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGrownFor Context triple: [Beta vulgaris, isGrownFor, edible roots]
-
A.
isShadeGrown
Indicates that something (typically a crop or plant) is cultivated under the partial cover of shade rather than in direct, full sunlight.
-
B.
isHarvestedBy
Indicates that something (typically a resource, crop, or material) is collected or gathered through the actions of a particular agent or method.
-
C.
hasSecondaryGrowth
Indicates that an organism or structure undergoes secondary growth, meaning it increases in thickness or girth after its initial (primary) growth phase.
-
D.
isCultivatedAs
chosen
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
E.
hasClassifiedGrowth
Indicates that an entity has been assigned a specific growth category or type according to a defined classification system.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.