Triple
T27119704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLL Cup |
E686960
|
entity |
| Predicate | hasLanguageOfCompetition |
P11654
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [NLL Cup, hasLanguageOfCompetition, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfCompetition Context triple: [NLL Cup, hasLanguageOfCompetition, English]
-
A.
languageOfCompetition
chosen
Indicates the language in which a competition is conducted or officially presented.
-
B.
languageOfClubHeritage
Indicates the language traditionally associated with or used to represent a club’s cultural or historical heritage.
-
C.
hasOfficialLanguageAtVenue
Indicates that a specific language is officially designated for use at a particular venue or location.
-
D.
languageOfTeamCountry
Indicates that a particular language is the official or primary language used in the country to which a given team belongs.
-
E.
hasLanguageOfSide
Indicates that an entity uses or is associated with a particular language on a specific side or aspect (e.g., one side of a bilingual object or interface).
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 8:58 a.m.