Triple
T3068666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi Grand Prix |
E62166
|
entity |
| Predicate | typicalCalendarPosition |
P44231
|
FINISHED |
| Object | season finale |
—
|
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: season finale | Statement: [Abu Dhabi Grand Prix, typicalCalendarPosition, season finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCalendarPosition Context triple: [Abu Dhabi Grand Prix, typicalCalendarPosition, season finale]
-
A.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
B.
typicalRecipientPosition
Indicates the usual or expected spatial or organizational position where a recipient is located relative to the action or source.
-
C.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
D.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
E.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0ffcc208190962cc9edcbf43c31 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f7630c81908e1ca8a69611cff6 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.