Triple
T8065891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala Blasters FC |
E188241
|
entity |
| Predicate | hasReachedISLFinal |
P80303
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kerala Blasters FC, hasReachedISLFinal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReachedISLFinal Context triple: [Kerala Blasters FC, hasReachedISLFinal, yes]
-
A.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
B.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
C.
hasQuarterFinalStage
Indicates that a competition or event includes a quarter-final stage in its structure.
-
D.
isFinalEngagementOf
Indicates that a given engagement is the last or concluding engagement in a sequence or series of engagements involving the same entities.
-
E.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff5547c8190a7ec5958a23e302f |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:26 p.m.