Triple
T32435756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aki basho |
E828859
|
entity |
| Predicate | heldAtVenueSince |
P174475
|
FINISHED |
| Object | Ryōgoku Kokugikan (current building) era |
—
|
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: Ryōgoku Kokugikan (current building) era | Statement: [Aki basho, heldAtVenueSince, Ryōgoku Kokugikan (current building) era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldAtVenueSince Context triple: [Aki basho, heldAtVenueSince, Ryōgoku Kokugikan (current building) era]
-
A.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
B.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
C.
firstHeldAtVenue
Indicates that an event was initially held at a particular venue for the first time.
-
D.
hasHostedVenue
Indicates that a particular venue has served as the location for hosting a specific event or activity.
-
E.
performedAtVenue
Indicates that an event or performance took place at a specific venue or location.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b48a8c8190a6ba0d2f084078cc |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:55 a.m.