Triple
T16266435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto3 |
E394886
|
entity |
| Predicate | predecessorClassEngineType |
P122432
|
FINISHED |
| Object | two-stroke 125 cc |
—
|
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: two-stroke 125 cc | Statement: [Moto3, predecessorClassEngineType, two-stroke 125 cc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorClassEngineType Context triple: [Moto3, predecessorClassEngineType, two-stroke 125 cc]
-
A.
predecessorClass
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
B.
predecessorSystemType
Indicates that one system type functioned as the predecessor or earlier version to another system type.
-
C.
predecessorModel
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
-
D.
predecessorSystem
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
E.
predecessorVersion
Indicates that one entity is an earlier or prior version in a version sequence relative to 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.