Triple

T4403688
Position Surface form Disambiguated ID Type / Status
Subject M561 Gama Goat E93674 entity
Predicate maximumRoadSpeed_kmh P2096 FINISHED
Object 80 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: 80 | Statement: [M561 Gama Goat, maximumRoadSpeed_kmh, 80]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumRoadSpeed_kmh
Context triple: [M561 Gama Goat, maximumRoadSpeed_kmh, 80]
  • A. maxSpeed chosen
    Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
  • B. speedLimitCharacteristic
    Indicates that an entity has a specific speed limit property or constraint associated with it.
  • C. hasSpeedLimit
    Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
  • D. hasSpeedLimitRange
    Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
  • E. regulatesSpeedLimitBy
    Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b352d1af608190ac06d50433cf24bb completed March 12, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69b34f5b36a881909bf2e970aa523390 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:28 p.m.