Triple
T19969610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manx Grand Prix |
E480034
|
entity |
| Predicate | courseUsedSince |
P138072
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [Manx Grand Prix, courseUsedSince, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseUsedSince Context triple: [Manx Grand Prix, courseUsedSince, 1923]
-
A.
courseUse
Indicates that a course employs, incorporates, or makes use of a particular resource, tool, or material in its instruction or structure.
-
B.
usesCourse
Indicates that one entity makes use of, applies, or relies on a particular course in some context or activity.
-
C.
formerCourseUsedFor
Indicates that one course previously served as preparation, credit, or a prerequisite fulfilling the role now associated with another course.
-
D.
coursePar
Indicates that two entities (such as paths, lines, or trajectories) run alongside each other in the same general direction without intersecting.
-
E.
hasBeenStudiedSince
Indicates that an entity has been the subject of study or research starting from a specified point in time and continuing thereafter.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc7c2fc81909b89c549a5f99e4c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.