Triple
T25365956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kıtalararası Derbi |
E636099
|
entity |
| Predicate | homeStadiumOfFenerbahçe |
P47009
|
FINISHED |
| Object | Şükrü Saracoğlu Stadium |
—
|
NE NERFINISHED |
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: Şükrü Saracoğlu Stadium | Statement: [Kıtalararası Derbi, homeStadiumOfFenerbahçe, Şükrü Saracoğlu Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumOfFenerbahçe Context triple: [Kıtalararası Derbi, homeStadiumOfFenerbahçe, Şükrü Saracoğlu Stadium]
-
A.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
B.
hostTeamStadium
chosen
Indicates that a particular team plays its home games at a specified stadium.
-
C.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
D.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
E.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10def5c81908f22e5a3c9f22af5 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:37 p.m.