Triple
T35753194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Grand Prix |
E1033370
|
entity |
| Predicate | wasRegularCalendarEventInDecade |
P97955
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [German Grand Prix, wasRegularCalendarEventInDecade, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRegularCalendarEventInDecade Context triple: [German Grand Prix, wasRegularCalendarEventInDecade, 1960s]
-
A.
heldInDecade
chosen
Indicates that an event or activity took place during a specific decade.
-
B.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
-
C.
isFrequentlyRecordedSinceDecade
Indicates that an entity has been commonly or regularly recorded starting from a specified decade.
-
D.
religiousEventYear
Indicates the calendar year in which a specified religious event took place or is scheduled to occur.
-
E.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.