Triple
T36796524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T53-L-1 |
E909197
|
entity |
| Predicate | usedWithAirframe |
P10706
|
FINISHED |
| Object | Bell Model 204 |
—
|
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: Bell Model 204 | Statement: [T53-L-1, usedWithAirframe, Bell Model 204]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithAirframe Context triple: [T53-L-1, usedWithAirframe, Bell Model 204]
-
A.
usedInVariantOfAircraft
Indicates that something (such as a component, system, or design feature) is utilized in a particular variant of an aircraft.
-
B.
usedOnAircraftName
chosen
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
C.
airframeDerivedFrom
Indicates that one airframe design is derived or developed from another pre-existing airframe design.
-
D.
airframeCommonalityWith
Indicates that two aircraft share the same or highly similar structural design and components in their airframes.
-
E.
airframe
Indicates that an entity is the structural framework or body of an aircraft associated with another entity (such as a specific model, component, or system).
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.