Triple
T16181181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valentino Rossi |
E392685
|
entity |
| Predicate | firstWorldTitleClass |
P122032
|
FINISHED |
| Object | 125cc |
—
|
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: 125cc | Statement: [Valentino Rossi, firstWorldTitleClass, 125cc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWorldTitleClass Context triple: [Valentino Rossi, firstWorldTitleClass, 125cc]
-
A.
resultedInFirstWorldTitleFor
Indicates that one entity’s achievement, event, or action caused another entity to obtain its first world championship title.
-
B.
firstTitleFor
Indicates that one entity is the earliest or primary title assigned to another entity, typically among multiple possible titles.
-
C.
firstPartTitle
Indicates that one entity is the first part or initial segment of the title of another entity.
-
D.
firstTitleSince
Indicates that an entity has achieved a particular title for the first time since a specified earlier point, event, or prior title occurrence.
-
E.
firstUseAsTitleBy
Indicates that an entity is the first to use a given term, phrase, or designation as a formal title for another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.