Triple

T35019808
Position Surface form Disambiguated ID Type / Status
Subject Boeing 737-600 E1010161 entity
Predicate sharesWingDesignWith P69276 FINISHED
Object Boeing 737-700 NE NERFINISHED

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: Boeing 737-700 | Statement: [Boeing 737-600, sharesWingDesignWith, Boeing 737-700]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesWingDesignWith
Context triple: [Boeing 737-600, sharesWingDesignWith, Boeing 737-700]
  • A. sharesDesignFeaturesWith chosen
    Indicates that two entities have similar or overlapping design characteristics, structures, or stylistic elements.
  • B. architectOfWing
    Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
  • C. hasWingPlanform
    Indicates the specific geometric shape or layout of an entity’s wing when viewed from above or below.
  • D. hasWingIn
    Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
  • E. sharesAircraftWith
    Indicates that two or more entities use, operate, or are associated with the same aircraft.
  • 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_69f76dcc3ac8819096a3ed52f5fa2523 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a004a8892c08190bcacb952ad737716 completed May 10, 2026, 9:06 a.m.
PD Predicate disambiguation batch_6a004a44b4948190be4b3dbfce8da020 completed May 10, 2026, 9:05 a.m.
Created at: May 3, 2026, 4:01 p.m.