Triple
T16266412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto3 |
E394886
|
entity |
| Predicate | engineDisplacementLimit |
P4162
|
FINISHED |
| Object | 250 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: 250 cc | Statement: [Moto3, engineDisplacementLimit, 250 cc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineDisplacementLimit Context triple: [Moto3, engineDisplacementLimit, 250 cc]
-
A.
engineDisplacement
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
-
B.
availableEngineDisplacement
chosen
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
-
C.
hasEngineDisplacementClass
Indicates a relationship where a vehicle or engine is assigned to a category based on the size or volume of its engine displacement.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
displacementPerCylinder
Indicates the volume of space displaced by the piston in a single cylinder during one complete stroke or cycle.
- 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_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. |
Created at: April 10, 2026, 5:05 a.m.