Triple
T35895269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brookvale |
E1038203
|
entity |
| Predicate | servesAsLocalSettingFor |
P15599
|
FINISHED |
| Object | Brookvale Community Centre |
—
|
NE NERFINISHED |
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: Brookvale Community Centre | Statement: [Brookvale, servesAsLocalSettingFor, Brookvale Community Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsLocalSettingFor Context triple: [Brookvale, servesAsLocalSettingFor, Brookvale Community Centre]
-
A.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
B.
usedAsSettingFor
chosen
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
-
C.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
D.
associatedWithSetting
Indicates that one entity is connected or linked to a particular context, environment, or setting in which it occurs or is relevant.
-
E.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: May 3, 2026, 4:06 p.m.