Triple
T8671652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YF-23 Black Widow II |
E205810
|
entity |
| Predicate | designedForCapability |
P55904
|
FINISHED |
| Object | supercruise |
—
|
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: supercruise | Statement: [YF-23 Black Widow II, designedForCapability, supercruise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForCapability Context triple: [YF-23 Black Widow II, designedForCapability, supercruise]
-
A.
capabilityType
chosen
Indicates the type or category of capability that an entity possesses or is associated with.
-
B.
developedCapability
Indicates that an entity has created, acquired, or brought into existence a particular capability through its actions or processes.
-
C.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
D.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
E.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491a34d08190b0795079d192a03d |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.