Triple
T16261863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 World Grand Prix |
E394772
|
entity |
| Predicate | hasQualifierEvents |
P122415
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [K-1 World Grand Prix, hasQualifierEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualifierEvents Context triple: [K-1 World Grand Prix, hasQualifierEvents, yes]
-
A.
hasQualifier
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
-
B.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
C.
qualifyingEvent
Indicates that an event meets specific conditions or criteria that make an entity eligible for a particular status, action, or outcome.
-
D.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
E.
hasEventDetail
Indicates that an event is associated with additional descriptive information or specific attributes that further characterize it.
- F. None of above. chosen
Provenance (4 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c4a0b08190af3574f087205afc |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.