Triple
T15508027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyber Lieutenant |
E379131
|
entity |
| Predicate | commandsUnder |
P27852
|
FINISHED |
| Object | Cyber Leader |
—
|
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: Cyber Leader | Statement: [Cyber Lieutenant, commandsUnder, Cyber Leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandsUnder Context triple: [Cyber Lieutenant, commandsUnder, Cyber Leader]
-
A.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
B.
commandCategory
Indicates that an action or command is classified into a specific category or type based on its function or purpose.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandsThrough
Indicates that one entity exercises authority or control over another indirectly, acting through an intermediary or chain of command.
-
E.
organizedUnder
chosen
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcea8888190a7b69aca360183c3 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:55 a.m.