Triple
T29627965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | love-in-idleness |
E755195
|
entity |
| Predicate | hasScientificNameOfPlant |
P138709
|
FINISHED |
| Object | Viola tricolor |
—
|
NE NERFINISHED |
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: Viola tricolor | Statement: [love-in-idleness, hasScientificNameOfPlant, Viola tricolor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificNameOfPlant Context triple: [love-in-idleness, hasScientificNameOfPlant, Viola tricolor]
-
A.
plantName
Indicates that the associated value is the name or designated label of a plant.
-
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.
hasPlantSymbol
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
-
D.
ortoBotanicoInstanceOf
Indicates that something is classified as an instance of an Orto Botanico (a specific botanical garden).
-
E.
hasScientificDesignation
chosen
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 6:39 p.m.