Triple
T7427248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Super League |
E171398
|
entity |
| Predicate | followsCompetitionFormat |
P2673
|
FINISHED |
| Object | league system |
—
|
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: league system | Statement: [Chinese Super League, followsCompetitionFormat, league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCompetitionFormat Context triple: [Chinese Super League, followsCompetitionFormat, league system]
-
A.
followsCompetition
Indicates that one entity participates in or occurs in a competition that takes place after or as a consequence of another specified competition.
-
B.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
C.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of a competition.
-
D.
establishedInCompetitionFormat
Indicates that something was created, founded, or set up within the context of a specific competition format or structure.
-
E.
formedForCompetition
Indicates that an entity was created or organized specifically to participate in a competition.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3055b7881908269ab909c5a85b5 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.