Triple
T7430654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princes Park |
E171479
|
entity |
| Predicate | cityStadiumRole |
P76364
|
FINISHED |
| Object | traditional suburban home ground of Carlton Football Club |
—
|
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: traditional suburban home ground of Carlton Football Club | Statement: [Princes Park, cityStadiumRole, traditional suburban home ground of Carlton Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStadiumRole Context triple: [Princes Park, cityStadiumRole, traditional suburban home ground of Carlton Football Club]
-
A.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
B.
cityOfStadium
Indicates that a stadium is located in, or primarily associated with, a particular city.
-
C.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
-
D.
stadiumCity
Indicates that a stadium is located in or associated with a particular city.
-
E.
stadiumFeature
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
- F. None of above. chosen
Provenance (4 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f32324c481908c9ba594e8456728 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:12 p.m.