Triple
T35795450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Australian Grand Prix |
E1034817
|
entity |
| Predicate | crashLapNumber |
P183680
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [2016 Australian Grand Prix, crashLapNumber, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crashLapNumber Context triple: [2016 Australian Grand Prix, crashLapNumber, 17]
-
A.
fatalAccidentLap
Indicates that a fatal accident occurred during a specific lap in a race or similar sequential event.
-
B.
safetyCarLaps
Indicates the number of laps in a race that were completed under safety car conditions.
-
C.
polePositionLapNumber
Indicates the specific lap number on which a competitor achieved the pole position time in a qualifying session.
-
D.
fastestLapLapNumber
Indicates the specific lap number on which the fastest lap was achieved in a race.
-
E.
raceNumberAtTrack
Indicates the specific ordinal number assigned to a race within the sequence of races held at a particular track.
- 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_69f7a25431b481908e39e953b207b6be |
completed | May 3, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a162672481909773f8383d91159a |
completed | May 3, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:06 p.m.