Triple

T19957992
Position Surface form Disambiguated ID Type / Status
Subject Supersport motorcycle E479736 entity
Predicate typicalEngineDisplacementRange P4162 FINISHED
Object 600cc to 1000cc 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: 600cc to 1000cc | Statement: [Supersport motorcycle, typicalEngineDisplacementRange, 600cc to 1000cc]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalEngineDisplacementRange
Context triple: [Supersport motorcycle, typicalEngineDisplacementRange, 600cc to 1000cc]
  • A. availableEngineDisplacement chosen
    Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
  • B. engineDisplacement
    Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
  • 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. engineTypeUsed
    Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65af1b32c81908ebe0e2570ec06a9 completed April 20, 2026, 4:57 p.m.
PD Predicate disambiguation batch_69e537f7e4848190b431a69ec3f1b609 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:54 p.m.