Triple
T3346580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-class destroyer |
E70387
|
entity |
| Predicate | hasCombatRole |
P9463
|
FINISHED |
| Object | screening capital ships |
—
|
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: screening capital ships | Statement: [K-class destroyer, hasCombatRole, screening capital ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombatRole Context triple: [K-class destroyer, hasCombatRole, screening capital ships]
-
A.
allowedCombatRoles
Indicates the combat roles that an entity is permitted or authorized to perform.
-
B.
mainCombatant
Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
-
C.
introducedToCombat
Indicates that something was brought into use or implemented specifically for the purpose of addressing or mitigating a particular problem, threat, or undesirable condition.
-
D.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
isCombinedArms
Indicates that multiple different types of military forces or capabilities are being used together in a coordinated, mutually supporting manner.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f4ff888190bf14b9b7fbe9bcee |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.