Triple
T1031356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing X-45 |
E22257
|
entity |
| Predicate | designedToDemonstrate |
P24206
|
FINISHED |
| Object | autonomous mission planning |
—
|
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: autonomous mission planning | Statement: [Boeing X-45, designedToDemonstrate, autonomous mission planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToDemonstrate Context triple: [Boeing X-45, designedToDemonstrate, autonomous mission planning]
-
A.
demonstratedConcept
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
B.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
C.
demonstratedAt
Indicates that an action, behavior, or capability was shown or exhibited at a particular event, location, or point in time.
-
D.
introducedAsDemonstrator
Indicates that one entity is presented or identified to another entity specifically in the role of a demonstrator.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- F. None of above. chosen
Provenance (4 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7276180819085c6b23501a6a6e0 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b95bb5908190ad1d5f5e0d8f664d |
completed | March 1, 2026, 10:10 p.m. |
Created at: March 1, 2026, 7:41 p.m.