Triple
T26205000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erythroxylum coca |
E655336
|
entity |
| Predicate | requiresSoil |
P32783
|
FINISHED |
| Object | well-drained soil |
—
|
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: well-drained soil | Statement: [Erythroxylum coca, requiresSoil, well-drained soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSoil Context triple: [Erythroxylum coca, requiresSoil, well-drained soil]
-
A.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
B.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
C.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
-
D.
soilRepresents
Indicates that one soil sample, type, or condition stands for, symbolizes, or serves as a proxy for another soil-related state or concept.
-
E.
cultivationRequirement
chosen
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 26, 2026, 8:50 p.m.