Triple
T28765515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengaluru FC |
E726255
|
entity |
| Predicate | continentalAchievement |
P179486
|
FINISHED |
| Object | AFC Cup runners-up 2016 |
—
|
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: AFC Cup runners-up 2016 | Statement: [Bengaluru FC, continentalAchievement, AFC Cup runners-up 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentalAchievement Context triple: [Bengaluru FC, continentalAchievement, AFC Cup runners-up 2016]
-
A.
continentalDominance
Indicates a relationship where one entity holds prevailing power, control, or influence over others within a specific continent.
-
B.
continentalQualifier
Indicates that something is qualified, categorized, or specified in terms of a particular continent or continental grouping.
-
C.
continentalAffiliation
Indicates the continent with which an entity (such as a country, region, or organization) is associated or belongs.
-
D.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
-
E.
continentCrossed
Indicates that an entity has traversed from one side of a continent to the other, crossing the continent’s landmass.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 6:13 a.m.