Triple
T34539522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool A (2019 Rugby World Cup) |
E886766
|
entity |
| Predicate | hostCityExample |
P90517
|
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: [Pool A (2019 Rugby World Cup), hostCityExample, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityExample Context triple: [Pool A (2019 Rugby World Cup), hostCityExample, Tokyo]
-
A.
hostCityOfEvent
chosen
Indicates that a city serves as the location where a particular event is held or takes place.
-
B.
hostCityLocatedOn
Indicates that the city serving as a host (e.g., of an event) is geographically situated on or along a specified physical feature or area (such as a river, coast, or region).
-
C.
hostCityOfEventParticipatedIn
Indicates that a city is the location where a particular event took place in which an entity participated.
-
D.
homeCityOfNOC
Indicates that a given city is the designated home or base city of a particular National Olympic Committee (NOC).
-
E.
hostCityInstanceOf
Indicates that a specific host city is an instance of a particular class or type of host city (e.g., Olympic host city, World Cup host city).
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72ad38a208190b4bdc828297f86ad |
completed | May 3, 2026, 11 a.m. |
| PD | Predicate disambiguation | batch_69f72a0243988190a43b8ea22457cd30 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 2:02 a.m.