Triple
T9909648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai Football Arena |
E185106
|
entity |
| Predicate | homeGroundInCompetition |
P74760
|
FINISHED |
| Object | Mumbai City FC in Indian Super League |
—
|
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: Mumbai City FC in Indian Super League | Statement: [Mumbai Football Arena, homeGroundInCompetition, Mumbai City FC in Indian Super League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundInCompetition Context triple: [Mumbai Football Arena, homeGroundInCompetition, Mumbai City FC in Indian Super League]
-
A.
homeGroundContext
chosen
Indicates the relationship between a sports team and the venue or location that serves as its primary home ground within a given contextual setting.
-
B.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
C.
homeStadiumInvolved
Indicates that an event, action, or relationship involves a team's home stadium as a relevant location or context.
-
D.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
E.
stateOfHomeGround
Indicates the location or region that serves as an entity’s primary home ground or base of operations.
- 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb51184d08190a0350f2722110811 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.