Triple
T1370704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Grand Prix |
E30106
|
entity |
| Predicate | firstHeldInMelbourne |
P6638
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Australian Grand Prix, firstHeldInMelbourne, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldInMelbourne Context triple: [Australian Grand Prix, firstHeldInMelbourne, 1996]
-
A.
firstEditionHeldIn
chosen
Indicates the location where the first edition or initial occurrence of an event was held.
-
B.
firstCeremony
Indicates that an entity participates in or is associated with the earliest or initial ceremony in a sequence or context.
-
C.
firstHeldAsSeparateTournament
Indicates that an event was initially conducted as an independent, standalone tournament rather than as part of another competition.
-
D.
firstHeldInOmaha
Indicates that the first occurrence or edition of an event or activity took place in Omaha.
-
E.
isFirstWorldCupHeldIn
Indicates that a country's first participation in the FIFA World Cup took place in the specified host nation or location.
- 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.