Triple
T28991102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 São Paulo Grand Prix qualifying |
E736026
|
entity |
| Predicate | redFlagSession |
P63717
|
FINISHED |
| Object | 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: Q3 | Statement: [2022 São Paulo Grand Prix qualifying, redFlagSession, Q3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redFlagSession Context triple: [2022 São Paulo Grand Prix qualifying, redFlagSession, Q3]
-
A.
redFlags
Indicates that one entity identifies or associates warning signs, concerns, or problematic indicators with another entity or situation.
-
B.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
C.
inscriptionSession
Indicates a relationship where an inscription is created, recorded, or associated within a particular session or event of inscribing.
-
D.
sessionNotation
chosen
Indicates a notation or labeling that is specifically associated with a particular session or occurrence of an event.
-
E.
inSessionDuring
Indicates that an entity is actively engaged in or part of a session throughout a specified time period.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7d3b5c8190937aaddff2879989 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:25 a.m.