Triple
T35929444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese national Olympic teams |
E1039117
|
entity |
| Predicate | hasSummerHostCity |
P7898
|
FINISHED |
| Object | Tokyo |
—
|
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: Tokyo | Statement: [Japanese national Olympic teams, hasSummerHostCity, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummerHostCity Context triple: [Japanese national Olympic teams, hasSummerHostCity, Tokyo]
-
A.
hasHostCity
chosen
Indicates that a particular event, organization, or activity is located in or officially hosted by a specific city.
-
B.
hasCoHostCity
Indicates that an event is jointly hosted or organized by the specified city alongside one or more other cities.
-
C.
hasHostCityStatus
Indicates that a city holds the official designation or role of hosting a particular event, organization, or function.
-
D.
previousSummerGamesYearInHostCity
Indicates that the given year is the year when the previous Summer Olympic Games were held in the same host city.
-
E.
hostCityNumberOfTimesHostedSummerGames
Indicates how many times a particular city has hosted the Summer Olympic Games.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:07 p.m.