Triple
T36172700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myth of Malham Race |
E1046187
|
entity |
| Predicate | isInCalendarOf |
P114346
|
FINISHED |
| Object | Royal Ocean Racing Club |
—
|
NE NERFINISHED |
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: Royal Ocean Racing Club | Statement: [Myth of Malham Race, isInCalendarOf, Royal Ocean Racing Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCalendarOf Context triple: [Myth of Malham Race, isInCalendarOf, Royal Ocean Racing Club]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
isFollowedInCalendarBy
Indicates that one event or time period occurs immediately after another in a calendar sequence.
-
C.
usesCalendarEvent
Indicates that one entity makes use of, interacts with, or relies on a specific calendar event.
-
D.
partOfCalendar
chosen
Indicates that one temporal element (such as an event, date, or period) belongs to, is contained within, or is scheduled as a component of a particular calendar.
-
E.
followsCalendarOf
Indicates that one entity adopts and adheres to the scheduling, events, or time structure defined by another entity’s calendar.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.