Triple

T871269
Position Surface form Disambiguated ID Type / Status
Subject Douglas X-3 Stiletto E18817 entity
Predicate reasonForPerformanceLimitation P20676 FINISHED
Object underpowered engines 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: underpowered engines | Statement: [Douglas X-3 Stiletto, reasonForPerformanceLimitation, underpowered engines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForPerformanceLimitation
Context triple: [Douglas X-3 Stiletto, reasonForPerformanceLimitation, underpowered engines]
  • A. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • B. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • C. limitedSystemType
    Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
  • D. gLimit
    Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
  • E. reasonForElimination
    Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
  • 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_69a4938db1f081909bcd1ad2713b6096 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac94d5ac81909feee876696da589 completed March 1, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69a4aa89ca008190b50d061ac7fe19f9 completed March 1, 2026, 9:07 p.m.
PDg Predicate description generation batch_69a4ab4a38ec8190915916d80299ab55 completed March 1, 2026, 9:10 p.m.
Created at: March 1, 2026, 7:39 p.m.