Triple
T5637135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Exhibition Building and Carlton Gardens |
E147974
|
entity |
| Predicate | gardenFeatures |
P22782
|
FINISHED |
| Object | tree-lined avenues |
—
|
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-lined avenues | Statement: [Royal Exhibition Building and Carlton Gardens, gardenFeatures, tree-lined avenues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenFeatures Context triple: [Royal Exhibition Building and Carlton Gardens, gardenFeatures, tree-lined avenues]
-
A.
gardenFeature
chosen
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
B.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
C.
gardenAccessibility
Indicates how easily people can enter, move through, and use a garden space, considering factors like paths, entrances, and accommodations for different mobility needs.
-
D.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
E.
rockGardenDesignFeature
Indicates that something serves as a design feature or element within a rock garden.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022809f708190ab859aa446683b10 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.