Triple
T7118613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fern Gully (Royal Botanic Gardens Victoria) |
E165884
|
entity |
| Predicate | isShadedBy |
P51692
|
FINISHED |
| Object | tree canopy |
—
|
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: tree canopy | Statement: [Fern Gully (Royal Botanic Gardens Victoria), isShadedBy, tree canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShadedBy Context triple: [Fern Gully (Royal Botanic Gardens Victoria), isShadedBy, tree canopy]
-
A.
shaded
chosen
Indicates that one entity partially or fully blocks light from reaching another, resulting in the latter being in shadow.
-
B.
isShadeGrown
Indicates that something (typically a crop or plant) is cultivated under the partial cover of shade rather than in direct, full sunlight.
-
C.
isShadeOf
Indicates that one entity represents a specific tonal or color variation derived from or closely related to another entity.
-
D.
obscuredIn
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
-
E.
overshadowedBy
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
- 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.