Triple
T1296821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suncorp Stadium |
E27670
|
entity |
| Predicate | underwentRedevelopment |
P11204
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Suncorp Stadium, underwentRedevelopment, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentRedevelopment Context triple: [Suncorp Stadium, underwentRedevelopment, early 2000s]
-
A.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
B.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
C.
largelyRebuilt
chosen
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
D.
siteRedevelopedAs
Indicates that a site has been transformed, rebuilt, or repurposed into a new form, function, or development.
-
E.
renovatedFrom
Indicates that one entity has been updated, improved, or restored by modifying or reworking an earlier version represented by another 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.