Triple
T33442089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Anyang |
E856389
|
entity |
| Predicate | homeStadiumUsedSince |
P176631
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [FC Anyang, homeStadiumUsedSince, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumUsedSince Context triple: [FC Anyang, homeStadiumUsedSince, 2013]
-
A.
homeTeamStadiumUsed
Indicates that a particular stadium is used as the home venue by a specified home team.
-
B.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
C.
homeStadiumUsedForEvent
Indicates that a particular stadium, serving as a team or organization's home venue, is used to host a specific event.
-
D.
homeStadiumConstructed
Indicates that a particular stadium was built or constructed specifically to serve as the home venue for a given team or organization.
-
E.
stadiumOpeningYear
Indicates the calendar year in which a stadium was officially opened for use.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:37 a.m.