Triple
T32382967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Stadium (Tokyo) |
E827470
|
entity |
| Predicate | mainStadiumFor |
P70079
|
FINISHED |
| Object | 1964 Summer Olympics |
—
|
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: 1964 Summer Olympics | Statement: [National Stadium (Tokyo), mainStadiumFor, 1964 Summer Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStadiumFor Context triple: [National Stadium (Tokyo), mainStadiumFor, 1964 Summer Olympics]
-
A.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
B.
stadiumFor
chosen
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
C.
mainCityStadium
Indicates that a stadium serves as the primary or main stadium for a given city.
-
D.
mainStadiumLocatedIn
Indicates that the primary stadium associated with an entity is geographically situated within a specified location.
-
E.
keyStadium
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 12:51 a.m.