Triple
T14818587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 6X |
E348382
|
entity |
| Predicate | manufacturerClaim |
P5171
|
FINISHED |
| Object | ultra-widebody business jet |
—
|
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: ultra-widebody business jet | Statement: [Falcon 6X, manufacturerClaim, ultra-widebody business jet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturerClaim Context triple: [Falcon 6X, manufacturerClaim, ultra-widebody business jet]
-
A.
manufacturerStatus
Indicates the current operational or business condition of a manufacturer in relation to the product or agreement in question.
-
B.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
-
C.
marketingClaim
chosen
Indicates that an entity asserts or promotes a statement about a product, service, or offering for marketing or advertising purposes.
-
D.
formerManufacturer
Indicates that an entity previously manufactured another entity but no longer does so.
-
E.
manufacturedBy
Indicates that an item or product is produced or created by a specific manufacturer or maker.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe4cf38819090f25ef045351d5d |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:50 a.m.