Triple
T1622718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai City FC |
E35067
|
entity |
| Predicate | homeCountryCode |
P1083
|
FINISHED |
| Object | IN |
—
|
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: IN | Statement: [Mumbai City FC, homeCountryCode, IN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryCode Context triple: [Mumbai City FC, homeCountryCode, IN]
-
A.
postalCountry
Indicates the country associated with an entity’s postal or mailing address.
-
B.
associatedCountry
chosen
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
-
C.
residenceCountry
Indicates the country in which an entity lives or has their primary place of residence.
-
D.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
E.
countryOrRegion
Indicates that one entity is a country or geographic region associated with another entity (such as its location, jurisdiction, or area of relevance).
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.