Triple
T3802145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Aircraft Company |
E91712
|
entity |
| Predicate | aircraftTypeProduced |
P19270
|
FINISHED |
| Object | twin-engine business jets |
—
|
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: twin-engine business jets | Statement: [Honda Aircraft Company, aircraftTypeProduced, twin-engine business jets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeProduced Context triple: [Honda Aircraft Company, aircraftTypeProduced, twin-engine business jets]
-
A.
aircraftModelProduced
Indicates that a specific aircraft model has been manufactured or produced by a particular entity (such as a company or organization).
-
B.
aircraftConfigurationProduced
chosen
Indicates that a specific aircraft configuration has been manufactured or produced.
-
C.
aircraftEngineTypeProduced
Indicates that a particular type of aircraft engine is manufactured or produced by a specified entity.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
developedAircraft
Indicates that an entity (such as a person or organization) was responsible for designing, creating, or engineering a particular aircraft.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.