Triple
T36717184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodbye, Moscow |
E906942
|
entity |
| Predicate | locationOfFirstMajorPerformance |
P58338
|
FINISHED |
| Object | Luzhniki Stadium |
E203251
|
NE 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: Luzhniki Stadium | Statement: [Goodbye, Moscow, locationOfFirstMajorPerformance, Luzhniki Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFirstMajorPerformance Context triple: [Goodbye, Moscow, locationOfFirstMajorPerformance, Luzhniki Stadium]
-
A.
dateOfFirstMajorConcert
Indicates the calendar date on which an entity held its first significant or large-scale concert performance.
-
B.
firstUSPerformanceLocation
Indicates the location where an entity was first performed in the United States.
-
C.
firstPerformanceAt
chosen
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
D.
firstPerformanceLocationOfWorkAppearingIn
Indicates the location where a work was first performed or premiered.
-
E.
firstPerformanceCityOfWork
Indicates the city where a particular work was first performed.
- F. None of above.
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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a383578748190b64fa169172c6a90 |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.