Triple
T1061172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanshin Koshien Stadium |
E22909
|
entity |
| Predicate | builtToCommemorate |
P7860
|
FINISHED |
| Object | Emperor Taishō’s enthronement |
—
|
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: Emperor Taishō’s enthronement | Statement: [Hanshin Koshien Stadium, builtToCommemorate, Emperor Taishō’s enthronement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtToCommemorate Context triple: [Hanshin Koshien Stadium, builtToCommemorate, Emperor Taishō’s enthronement]
-
A.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
B.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
C.
commemoratedPerson
chosen
Indicates that the subject serves as a memorial or tribute to the referenced person.
-
D.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
E.
commemoratesEventDescribedIn
Indicates that something serves to honor or remember an event that is described in a particular source or representation.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.