Triple
T12594247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Rectangular Stadium |
E300692
|
entity |
| Predicate | purposeBuiltFor |
P8196
|
FINISHED |
| Object | rectangular-field sports |
—
|
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: rectangular-field sports | Statement: [Melbourne Rectangular Stadium, purposeBuiltFor, rectangular-field sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeBuiltFor Context triple: [Melbourne Rectangular Stadium, purposeBuiltFor, rectangular-field sports]
-
A.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
B.
isBuiltFor
chosen
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
C.
primarilyFor
Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
-
D.
meetsForPurpose
Indicates that one entity meets with another specifically to pursue or accomplish a particular purpose or objective.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.