Triple
T16181029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teams World Championship |
E392682
|
entity |
| Predicate | pointsSystemBasedOn |
P64949
|
FINISHED |
| Object | MotoGP race results |
—
|
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: MotoGP race results | Statement: [Teams World Championship, pointsSystemBasedOn, MotoGP race results]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsSystemBasedOn Context triple: [Teams World Championship, pointsSystemBasedOn, MotoGP race results]
-
A.
pointsSystemManagedBy
Indicates that the points system is overseen, controlled, or administered by a specified managing entity.
-
B.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
C.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
D.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
E.
usesPointsSystem
chosen
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.