Triple
T3560804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro RJX |
E75331
|
entity |
| Predicate | airframeBasis |
P17752
|
FINISHED |
| Object | derived from Avro RJ |
—
|
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: derived from Avro RJ | Statement: [Avro RJX, airframeBasis, derived from Avro RJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airframeBasis Context triple: [Avro RJX, airframeBasis, derived from Avro RJ]
-
A.
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).
-
B.
airframeDerivedFrom
chosen
Indicates that one airframe design is derived or developed from another pre-existing airframe design.
-
C.
airframeConstruction
Indicates the method or structural approach used to build an aircraft’s main body and supporting framework.
-
D.
aircraftBuilder
Indicates that one entity is the manufacturer or constructor responsible for building the aircraft represented by the other entity.
-
E.
architectOfWing
Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc08ac1b0819082021ecdd0061dc3 |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.