Triple

T29817225
Position Surface form Disambiguated ID Type / Status
Subject Pacific E757142 entity
Predicate hasDesignAdvantage P194311 FINISHED
Object ability to carry wide firebox behind driving wheels 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: ability to carry wide firebox behind driving wheels | Statement: [Pacific, hasDesignAdvantage, ability to carry wide firebox behind driving wheels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDesignAdvantage
Context triple: [Pacific, hasDesignAdvantage, ability to carry wide firebox behind driving wheels]
  • A. hasDesign
    Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
  • B. hasDesignOption
    Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
  • C. hasDesignSignificance
    Indicates that something possesses notable importance, impact, or relevance specifically in terms of its design.
  • D. designedFeature
    Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
  • E. hasDesignConsideration
    Indicates that one entity takes another entity into account as a factor, constraint, or requirement in its design or planning.
  • 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_69f2245701c88190ad42415a0956c4ed completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fd6a1c1c4881908090053bc359b181 completed May 8, 2026, 4:44 a.m.
PD Predicate disambiguation batch_69fd696f24d8819091033afacbdaadc5 completed May 8, 2026, 4:41 a.m.
PDg Predicate description generation batch_69fd6a1a38f081908c573aee4696de4f completed May 8, 2026, 4:44 a.m.
Created at: April 29, 2026, 5:27 p.m.