Triple
T35526802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEG |
E1026691
|
entity |
| Predicate | notableTournamentSeries |
P207029
|
FINISHED |
| Object | K-1 World Grand Prix |
E394772
|
NE 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: K-1 World Grand Prix | Statement: [FEG, notableTournamentSeries, K-1 World Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTournamentSeries Context triple: [FEG, notableTournamentSeries, K-1 World Grand Prix]
-
A.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
B.
notableTournamentCategory
Indicates that an entity is associated with a tournament that is particularly notable or significant within a specified category or type.
-
C.
notableTournamentHosted
Indicates that an entity has served as the host or venue for a tournament considered notable or significant.
-
D.
notableGameSeries
Indicates that there exists a game series for which the subject is notably recognized or strongly associated.
-
E.
majorTournament
Indicates that an event is classified as a major, high-prestige tournament within its competitive domain.
- F. None of above. chosen
Provenance (5 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852e7f2c08190900446e5cc7f6aad |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.