Triple
T1037747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737 |
E22402
|
entity |
| Predicate | engineMounting |
P22132
|
FINISHED |
| Object | underwing pylons |
—
|
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: underwing pylons | Statement: [Boeing 737, engineMounting, underwing pylons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineMounting Context triple: [Boeing 737, engineMounting, underwing pylons]
-
A.
enginePlacement
chosen
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
B.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
C.
engineSupplier
Indicates a relationship where one entity supplies or provides engines to another entity.
-
D.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
E.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.