Triple
T8671571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raptor |
E205808
|
entity |
| Predicate | associatedWithCapability |
P56209
|
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: [Raptor, associatedWithCapability, supercruise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCapability Context triple: [Raptor, associatedWithCapability, supercruise]
-
A.
associatedCapability
chosen
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
-
B.
providesCapabilityTo
Indicates that one entity enables or equips another entity with a specific capability or functionality.
-
C.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
D.
isPartOfCapability
Indicates that one capability is a component or sub-function within a broader, composite capability.
-
E.
associatedWithPrivilege
Indicates a relationship where an entity is linked to, granted, or operates under a specific privilege or set of privileges.
- 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.