Triple
T2016839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pueblo chile |
E44013
|
entity |
| Predicate | botanicalSpecies |
P21608
|
FINISHED |
| Object | Capsicum annuum |
—
|
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: Capsicum annuum | Statement: [Pueblo chile, botanicalSpecies, Capsicum annuum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: botanicalSpecies Context triple: [Pueblo chile, botanicalSpecies, Capsicum annuum]
-
A.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
B.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
C.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
D.
hasBotanicalResource
chosen
Indicates that an entity possesses, contains, or is associated with a plant-based resource (such as plants, plant parts, or botanical materials) used for some purpose.
-
E.
plantKingdom
Indicates that the subject belongs to, or is classified within, the plant kingdom.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ccdb7c81909f6b3c96f79fcdfc |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.