Triple
T582786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toowoomba |
E15092
|
entity |
| Predicate | hasBotanicalFeature |
P3481
|
FINISHED |
| Object | extensive public parks and gardens |
—
|
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: extensive public parks and gardens | Statement: [Toowoomba, hasBotanicalFeature, extensive public parks and gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBotanicalFeature Context triple: [Toowoomba, hasBotanicalFeature, extensive public parks and gardens]
-
A.
flowerCharacteristic
Indicates that a flower possesses a particular attribute, quality, or feature (such as color, shape, size, or scent).
-
B.
hasPlantSymbol
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
-
C.
hasBotanicalGarden
chosen
Indicates that one entity possesses, contains, or includes a botanical garden as part of its facilities or domain.
-
D.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
E.
hasRhizoids
Indicates that an organism possesses rhizoids, i.e., root-like structures used for anchorage or absorption.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.