Triple
T35862988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airén |
E1037004
|
entity |
| Predicate | plantingDensity |
P9738
|
FINISHED |
| Object | traditionally low-density bush vines |
—
|
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: traditionally low-density bush vines | Statement: [Airén, plantingDensity, traditionally low-density bush vines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantingDensity Context triple: [Airén, plantingDensity, traditionally low-density bush vines]
-
A.
minimumPlantingDensity
Indicates the smallest allowable number of plants per unit area at which planting should occur.
-
B.
higherPlantingDensityThan
Indicates that one entity is planted at a greater density (more individuals per unit area) than another entity.
-
C.
numberOfPlants
Indicates the total count of plants associated with a given entity or context.
-
D.
plantingStyle
chosen
Indicates the method or arrangement used to plant entities in relation to each other or their environment.
-
E.
globalPlantings
Indicates a relationship where plantings or cultivation activities are distributed or carried out across multiple countries or worldwide locations.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.