Triple
T1370741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Grand Prix |
E30106
|
entity |
| Predicate | fanActivities |
P8834
|
FINISHED |
| Object | pit lane walk in selected sessions |
—
|
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: pit lane walk in selected sessions | Statement: [Australian Grand Prix, fanActivities, pit lane walk in selected sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanActivities Context triple: [Australian Grand Prix, fanActivities, pit lane walk in selected sessions]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanbaseCharacteristic
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
C.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
-
D.
activityType
chosen
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
- 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.