Triple
T32765198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Farragut (DDG-99) |
E837874
|
entity |
| Predicate | hasAegisCombatSystem |
P73205
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USS Farragut (DDG-99), hasAegisCombatSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAegisCombatSystem Context triple: [USS Farragut (DDG-99), hasAegisCombatSystem, yes]
-
A.
usesCombatSystem
chosen
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
B.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
C.
hasCombatType
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
-
D.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
-
E.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.