Triple
T37491840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalbarri |
E931709
|
entity |
| Predicate | floraInterest |
P83264
|
FINISHED |
| Object | seasonal wildflowers |
—
|
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: seasonal wildflowers | Statement: [Kalbarri, floraInterest, seasonal wildflowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraInterest Context triple: [Kalbarri, floraInterest, seasonal wildflowers]
-
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.
hasBotanicalInterest
Indicates that one entity has a particular interest or concern in the botanical characteristics, study, or cultivation of another entity.
-
C.
studiedFloraOf
Indicates that a subject conducted research or examination on the plant life (flora) of a specified object or region.
-
D.
floralDiversity
Indicates the variety and richness of different flower or plant species present in a given area or context.
-
E.
botanicalSignificance
Indicates the importance or relevance of one entity to another in a botanical or plant-related context.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.