Triple
T27797536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Italian Cup |
E702154
|
entity |
| Predicate | featuredLeagueLevel |
P37877
|
FINISHED |
| Object | top-tier clubs (early editions) |
—
|
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: top-tier clubs (early editions) | Statement: [Anglo-Italian Cup, featuredLeagueLevel, top-tier clubs (early editions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredLeagueLevel Context triple: [Anglo-Italian Cup, featuredLeagueLevel, top-tier clubs (early editions)]
-
A.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
B.
associatedLeagueLevel
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
C.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
D.
stateLeagueLevel
Indicates the competitive tier or division level of a league within a particular state’s league system.
-
E.
featuredCompetitionLevel
chosen
Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 27, 2026, 5:32 p.m.