Triple
T28046579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Stadium |
E708699
|
entity |
| Predicate | capacityRugby |
P163659
|
FINISHED |
| Object | approximately 49,000 |
—
|
LITERAL 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: approximately 49,000 | Statement: [Tokyo Stadium, capacityRugby, approximately 49,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityRugby Context triple: [Tokyo Stadium, capacityRugby, approximately 49,000]
-
A.
codeOfRugby
Indicates that one entity is the specific code or variant of rugby (e.g., rugby union, rugby league) under which the other entity is played, governed, or classified.
-
B.
capacityForWorldCup
Indicates the maximum number of spectators a venue can accommodate specifically for World Cup events.
-
C.
roleInRugby
Indicates the specific position or function an entity holds within the context of playing or participating in rugby.
-
D.
representsInWorldRugby
Indicates that an entity serves as an official representative or member within the organizational structure of World Rugby.
-
E.
playedRugbyUnionFor
Indicates that one entity was a member of and competed for a particular rugby union team or organization.
- F. None of above. chosen
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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63f342abc8190bc64e5d54d0ddacf |
completed | May 2, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:30 p.m.