Triple
T25410104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth Games Village, Melbourne |
E636666
|
entity |
| Predicate | postGamesDevelopment |
P35253
|
FINISHED |
| Object | mixed-use development |
—
|
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: mixed-use development | Statement: [Commonwealth Games Village, Melbourne, postGamesDevelopment, mixed-use development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postGamesDevelopment Context triple: [Commonwealth Games Village, Melbourne, postGamesDevelopment, mixed-use development]
-
A.
postGamesDevelopment
Indicates that an entity publishes or shares information about the development progress or updates of games.
-
B.
postGamesUse
chosen
Indicates that an entity uses or engages with something after games have concluded.
-
C.
games
Indicates that one entity participates in, is associated with, or is characterized by playing or engaging in games with another entity.
-
D.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
E.
homeGamesOf
Indicates that the subject is a home game (or set of home games) played by the specified team or entity.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00d2924819082adfdfea936a4ef |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:53 p.m.