Triple
T13426413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Turkey |
E313492
|
entity |
| Predicate | WRCCalendarReturn |
P109871
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Rally Turkey, WRCCalendarReturn, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WRCCalendarReturn Context triple: [Rally Turkey, WRCCalendarReturn, 2018]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
C.
holidaySchedule
Indicates the planned dates, times, and durations during which holidays occur or are observed.
-
D.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
-
E.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.