Triple
T1043835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing X-48 |
E22529
|
entity |
| Predicate | intendedApplication |
P12134
|
FINISHED |
| Object | future military transport aircraft |
—
|
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: future military transport aircraft | Statement: [Boeing X-48, intendedApplication, future military transport aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedApplication Context triple: [Boeing X-48, intendedApplication, future military transport aircraft]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
C.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69a4b8475ab48190848388eea6448cb6 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.