Triple
T1370715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Grand Prix |
E30106
|
entity |
| Predicate | safetyCarFrequency |
P27049
|
FINISHED |
| Object | relatively high for F1 |
—
|
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: relatively high for F1 | Statement: [Australian Grand Prix, safetyCarFrequency, relatively high for F1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyCarFrequency Context triple: [Australian Grand Prix, safetyCarFrequency, relatively high for F1]
-
A.
safetyCarSupplier
Indicates that one entity serves as the provider or manufacturer of safety cars for another entity or event.
-
B.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
D.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
-
E.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
- 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_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. |
| PDg | Predicate description generation | batch_69a4bfc2134c81909cbaaa151d96e9a8 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:57 p.m.