Triple
T33924564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Type 200 |
E869711
|
entity |
| Predicate | aircraftTypeStatus |
P150445
|
FINISHED |
| Object | unbuilt aircraft design |
—
|
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: unbuilt aircraft design | Statement: [Bristol Type 200, aircraftTypeStatus, unbuilt aircraft design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeStatus Context triple: [Bristol Type 200, aircraftTypeStatus, unbuilt aircraft design]
-
A.
aircraftStatus
Indicates the current operational condition or state of an aircraft (e.g., active, grounded, in maintenance, or decommissioned).
-
B.
aircraftTypeManaged
Indicates that one entity is responsible for managing or overseeing a particular type or category of aircraft.
-
C.
aircraftOperationType
Indicates the specific manner or purpose for which an aircraft is being operated (e.g., commercial, private, military, training).
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
subjectAircraftProductionStatus
chosen
Indicates the current stage or condition of an aircraft’s production process in relation to the subject.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:49 a.m.