Triple
T38365922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NACK5 Stadium Omiya |
E892438
|
entity |
| Predicate | isFootballSpecific |
P39551
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NACK5 Stadium Omiya, isFootballSpecific, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFootballSpecific Context triple: [NACK5 Stadium Omiya, isFootballSpecific, true]
-
A.
typeOfFootball
Indicates the specific code or variant of football that characterizes or classifies a given football-related entity.
-
B.
convertedToFootballOnly
chosen
Indicates that something previously involved in multiple activities or sports has been changed so that it is now used exclusively for football.
-
C.
hasFootballTheme
Indicates that something is characterized by or centered around the sport of football as a primary theme.
-
D.
hasFootballAssociation
Indicates that there exists an affiliation or formal relationship between an entity and a football (soccer) association or governing body.
-
E.
associationFootballBranchOf
Indicates a formal organizational relationship in which an association football entity operates as a subordinate branch or division of a larger parent organization.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.