Triple

T13180422
Position Surface form Disambiguated ID Type / Status
Subject General Electric CT7 E313706 entity
Predicate familyMember P566 FINISHED
Object CT7-6 E1026177 NE 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: CT7-6 | Statement: [General Electric CT7, familyMember, CT7-6]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CT7-6
Context triple: [General Electric CT7, familyMember, CT7-6]
  • A. CT7-2 chosen
    CT7-2 is a specific variant of General Electric’s CT7 turboshaft engine series, designed for use in medium-lift helicopters and similar aircraft.
  • B. CT7
    CT7 is a postcode district in the CT (Canterbury) postcode area of Kent, England, covering the village of Birchington-on-Sea and its surrounding localities.
  • C. CT1
    CT1 is a 3GPP working group responsible for specifying core network and terminal aspects of mobile telecommunications systems.
  • D. CT1
    CT1 is a central Canterbury postcode district in the CT area of southeast England, covering much of the historic city and its immediate surroundings.
  • E. CT8
    CT8 is a UK postal district within the CT (Canterbury) postcode area, covering part of the coastal town of Westgate-on-Sea in Kent, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d806ae1e08819090d95bfe1538cc17 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c490ed081908ea54edb25c3de90 completed April 10, 2026, 11:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f70a2e415481908ad1036376f702dc completed May 3, 2026, 8:41 a.m.
Created at: April 9, 2026, 9:14 p.m.