Triple
T26163733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Türk Telekom Arena |
E654186
|
entity |
| Predicate | openedAsHomeGroundFor |
P36076
|
FINISHED |
| Object | Galatasaray S.K. |
—
|
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: Galatasaray S.K. | Statement: [Türk Telekom Arena, openedAsHomeGroundFor, Galatasaray S.K.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsHomeGroundFor Context triple: [Türk Telekom Arena, openedAsHomeGroundFor, Galatasaray S.K.]
-
A.
denotesHomeGroundOf
Indicates that a particular location serves as the primary home ground or home venue for a specified team, organization, or entity.
-
B.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
C.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
D.
stateOfHomeGround
Indicates the location or region that serves as an entity’s primary home ground or base of operations.
-
E.
isHomeFieldOf
chosen
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 8:31 p.m.