Triple
T7118602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fern Gully (Royal Botanic Gardens Victoria) |
E165884
|
entity |
| Predicate | hasPlantGroup |
P68098
|
FINISHED |
| Object | ferns |
—
|
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: ferns | Statement: [Fern Gully (Royal Botanic Gardens Victoria), hasPlantGroup, ferns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlantGroup Context triple: [Fern Gully (Royal Botanic Gardens Victoria), hasPlantGroup, ferns]
-
A.
hasFloraGroup
chosen
Indicates that an entity is associated with, contains, or is characterized by a particular group or category of plant life.
-
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.
hasPlantPart
Indicates that one entity includes, contains, or is composed of a specific plant part of another entity.
-
E.
plantCollection
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61b8a288190a165ea25adfaaef5 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.