Triple
T35795453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Australian Grand Prix |
E1034817
|
entity |
| Predicate | qualifyingFormatSessions |
P184660
|
FINISHED |
| Object | Q1, Q2, Q3 |
—
|
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: Q1, Q2, Q3 | Statement: [2016 Australian Grand Prix, qualifyingFormatSessions, Q1, Q2, Q3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifyingFormatSessions Context triple: [2016 Australian Grand Prix, qualifyingFormatSessions, Q1, Q2, Q3]
-
A.
conferenceFormatUsed
Indicates that a particular conference is conducted using a specified format or modality (e.g., in-person, virtual, hybrid).
-
B.
conferenceFormat
Indicates the type or structure in which a conference is organized or conducted (e.g., in-person, virtual, hybrid, workshop-based).
-
C.
areDecisionMakingSessionsOf
Indicates that certain sessions function as the decision-making events or meetings associated with particular entities or processes.
-
D.
offersProgramFormat
Indicates that an entity provides or makes available a specific type or format of program.
-
E.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:06 p.m.