Triple
T22516170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graphilbum fragrans |
E556653
|
entity |
| Predicate | hasAromaticEpithet |
P121211
|
FINISHED |
| Object | fragrans |
—
|
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: fragrans | Statement: [Graphilbum fragrans, hasAromaticEpithet, fragrans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAromaticEpithet Context triple: [Graphilbum fragrans, hasAromaticEpithet, fragrans]
-
A.
isAromatic
Indicates that an entity possesses aromatic character, typically involving a conjugated ring system with delocalized electrons that confer special stability or scent-related properties.
-
B.
lessAromaticThan
Indicates that one entity has a lower degree of aromaticity than another entity.
-
C.
associatedWithEpithet
chosen
Indicates that an entity is linked to or described by a particular epithet or descriptive label.
-
D.
hasEpithetOrigin
Indicates that the origin or source of an epithet (a descriptive name or label) is specified for an entity.
-
E.
hasMeaningOfEpithet
Indicates that one entity expresses or conveys the meaning or sense of another entity’s epithet.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2cfc908190b3489228a1997f45 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.