Triple
T36129836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunzea |
E1044984
|
entity |
| Predicate | hasAromaticFoliage |
P196840
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kunzea, hasAromaticFoliage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAromaticFoliage Context triple: [Kunzea, hasAromaticFoliage, true]
-
A.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
B.
foliageCharacteristic
Indicates the specific traits or qualities of an entity’s foliage, such as its type, texture, color, or other distinguishing features.
-
C.
isAromaticVariety
Indicates that one entity is a variety or type of another that is specifically characterized by having a notable or distinctive aroma.
-
D.
hasVegetationRole
Indicates that an entity participates in or is assigned a specific functional role related to vegetation (such as growth, maintenance, or impact on plant life).
-
E.
hasFrondType
Indicates that one entity possesses or is characterized by a specific type or form of frond.
- F. None of above. chosen
Provenance (4 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: May 3, 2026, 4:08 p.m.