Triple
T1370734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Grand Prix |
E30106
|
entity |
| Predicate | typicalRaceDuration |
P18065
|
FINISHED |
| Object | around 90 to 120 minutes |
—
|
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: around 90 to 120 minutes | Statement: [Australian Grand Prix, typicalRaceDuration, around 90 to 120 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRaceDuration Context triple: [Australian Grand Prix, typicalRaceDuration, around 90 to 120 minutes]
-
A.
majorRaceDistance
Indicates the standard or primary distance over which a major race or competition is contested.
-
B.
raceDayIncludes
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
-
C.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
D.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
E.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d7b6008190bc0303b56959ba56 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.