Triple
T14219741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chōfu |
E352456
|
entity |
| Predicate | AjinomotoStadiumUsedFor |
P95893
|
FINISHED |
| Object | football matches |
—
|
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: football matches | Statement: [Chōfu, AjinomotoStadiumUsedFor, football matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AjinomotoStadiumUsedFor Context triple: [Chōfu, AjinomotoStadiumUsedFor, football matches]
-
A.
stadiumUsedFor
chosen
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
B.
usedAsOlympicStadiumFor
Indicates that a venue served as the official stadium for hosting events of a particular edition of the Olympic Games.
-
C.
operatesNationalStadiumFor
Indicates that one entity manages and runs the national stadium on behalf of another entity.
-
D.
usesBaseballStadium
Indicates that an entity regularly occupies or operates within a particular baseball stadium as its primary venue or facility.
-
E.
hasStadiumUse
Indicates that one entity (typically a team, organization, or event) uses or is authorized to use a particular stadium for its activities or purposes.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de621258d4819085f358cd2cf109e4 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.