Triple
T12153480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plumbago |
E289514
|
entity |
| Predicate | regionOfHorticulturalUse |
P50898
|
FINISHED |
| Object | Mediterranean climates |
—
|
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: Mediterranean climates | Statement: [Plumbago, regionOfHorticulturalUse, Mediterranean climates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfHorticulturalUse Context triple: [Plumbago, regionOfHorticulturalUse, Mediterranean climates]
-
A.
cultivatedInRegion
Indicates that something (such as a crop or plant) is grown or produced through cultivation within a specified geographic region.
-
B.
plantUse
Indicates that a plant is used for a particular purpose, function, or application.
-
C.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
-
D.
usedInHorticultureGenus
chosen
Indicates that something (such as a plant, substance, or technique) is employed within horticultural practices involving a particular genus.
-
E.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.