Triple
T29037991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 36 |
E737916
|
entity |
| Predicate | locationChangeFrom |
P49285
|
FINISHED |
| Object | Raymond James Stadium |
—
|
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: Raymond James Stadium | Statement: [WrestleMania 36, locationChangeFrom, Raymond James Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationChangeFrom Context triple: [WrestleMania 36, locationChangeFrom, Raymond James Stadium]
-
A.
positionChange
chosen
Indicates a change in an entity’s spatial or positional state from one location or configuration to another.
-
B.
locationProposedFrom
Indicates a proposed or suggested origin location from which something is expected or planned to come.
-
C.
namespaceChangedFrom
Indicates that an entity’s namespace has been modified, specifying the previous namespace it was changed from.
-
D.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
E.
locationRenamed
Indicates that a location has changed its name from one designation to another.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
Created at: April 28, 2026, 10 a.m.