Triple
T855854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea F.C. |
E18489
|
entity |
| Predicate | notableCompetitionLevel |
P18266
|
FINISHED |
| Object | top tier of English football |
—
|
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 of English football | Statement: [Chelsea F.C., notableCompetitionLevel, top tier of English football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompetitionLevel Context triple: [Chelsea F.C., notableCompetitionLevel, top tier of English football]
-
A.
primaryCompetitionLevel
chosen
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
B.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
C.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
D.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
E.
notableDivision
Indicates that one entity is a significant or prominent subdivision, branch, or section of another entity.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3c172481908ed164ee1579ec28 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.