Triple
T3832248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MotoGP |
E91039
|
entity |
| Predicate | hasQualifyingFormat |
P46686
|
FINISHED |
| Object | Q1 and Q2 sessions |
—
|
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 and Q2 sessions | Statement: [MotoGP, hasQualifyingFormat, Q1 and Q2 sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualifyingFormat Context triple: [MotoGP, hasQualifyingFormat, Q1 and Q2 sessions]
-
A.
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.
-
B.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
C.
hasMatchFormat
chosen
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
D.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
E.
hasFinalFormat
Indicates that an entity possesses or is associated with its completed, finalized version or representation.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8787bc8190819a7af975b609df |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.