Triple
T33227044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wattle Day |
E850581
|
entity |
| Predicate | associatedPlantGroup |
P83264
|
FINISHED |
| Object | Acacia species |
—
|
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: Acacia species | Statement: [Wattle Day, associatedPlantGroup, Acacia species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPlantGroup Context triple: [Wattle Day, associatedPlantGroup, Acacia species]
-
A.
associatedFlora
chosen
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
B.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
C.
seedPlantGroup
Indicates a relationship where a plant group is characterized by or associated with producing seeds as its means of reproduction.
-
D.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
E.
floweringPlantGroup
Indicates that the subject belongs to, or is classified within, a particular group or category of flowering plants.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.