Triple
T16026188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HondaJet |
E388723
|
entity |
| Predicate | engineMountConfiguration |
P92607
|
FINISHED |
| Object | over-the-wing engine mount |
—
|
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: over-the-wing engine mount | Statement: [HondaJet, engineMountConfiguration, over-the-wing engine mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineMountConfiguration Context triple: [HondaJet, engineMountConfiguration, over-the-wing engine mount]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
C.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
-
D.
aircraftEngineMounting
chosen
Indicates that an aircraft engine is attached or secured to a supporting structure or mounting point on the aircraft.
-
E.
engineConstructor
Indicates that an entity is the manufacturer or builder responsible for constructing a particular engine.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.