Triple
T17401215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dandenong Plaza |
E423090
|
entity |
| Predicate | hasPublicAmenities |
P79291
|
FINISHED |
| Object | restrooms |
—
|
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: restrooms | Statement: [Dandenong Plaza, hasPublicAmenities, restrooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicAmenities Context triple: [Dandenong Plaza, hasPublicAmenities, restrooms]
-
A.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
B.
typicalAmenity
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
-
C.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
D.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
E.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ac126788190b51323bde3c9ba69 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.