Triple
T1666144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Grand Prix |
E36015
|
entity |
| Predicate | qualifyingFormat |
P130
|
FINISHED |
| Object | knockout qualifying |
—
|
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: knockout qualifying | Statement: [Chinese Grand Prix, qualifyingFormat, knockout qualifying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifyingFormat Context triple: [Chinese Grand Prix, qualifyingFormat, knockout qualifying]
-
A.
qualifiesFrom
Indicates that one entity gains an official status, capability, or eligibility as a result of successfully completing or meeting the requirements of another entity.
-
B.
hasAwardedFormat
Indicates that one entity has granted or assigned a particular award format or type to another entity.
-
C.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
E.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa994f92b0819084ee2f6a672334b9 |
completed | March 6, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69a907d2475c8190b7ec7dccd3335eb1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.