Triple
T6099468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian floristic region |
E135957
|
entity |
| Predicate | hasNotableVegetationType |
P953
|
FINISHED |
| Object | sclerophyll forests |
—
|
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: sclerophyll forests | Statement: [Australian floristic region, hasNotableVegetationType, sclerophyll forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVegetationType Context triple: [Australian floristic region, hasNotableVegetationType, sclerophyll forests]
-
A.
vegetationType
chosen
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
C.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
D.
hasVegetationLayer
Indicates that an entity possesses a distinct layer or cover of vegetation as part of its structure or surface.
-
E.
hasVegetationIssue
Indicates that an entity is affected by a problem, damage, or abnormal condition related to its vegetation or plant life.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.