Triple
T4205910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreadnought-class submarine |
E86181
|
entity |
| Predicate | commandSystem |
P31624
|
FINISHED |
| Object | advanced combat management system |
—
|
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: advanced combat management system | Statement: [Dreadnought-class submarine, commandSystem, advanced combat management system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandSystem Context triple: [Dreadnought-class submarine, commandSystem, advanced combat management system]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandProcessor
chosen
Indicates that one entity is responsible for receiving, interpreting, and executing commands issued by another entity.
-
C.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
D.
commandServiceModule
Indicates that one entity issues commands to control or manage the operation of a service module.
-
E.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03844314819092639ed7d6ef2c6e |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af0196716c81908b99193690630a29 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.