Triple
T32410028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Duncan |
E828193
|
entity |
| Predicate | alliedNATODesignation |
P174048
|
FINISHED |
| Object | air-defence destroyer |
—
|
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: air-defence destroyer | Statement: [HMS Duncan, alliedNATODesignation, air-defence destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedNATODesignation Context triple: [HMS Duncan, alliedNATODesignation, air-defence destroyer]
-
A.
alliedDesignation
Indicates that one entity assigns or recognizes an allied status or designation for another entity.
-
B.
allianceDesignation
Indicates a formal relationship in which one entity designates or classifies another as an ally within an alliance.
-
C.
alliedCodeName
Indicates that one entity is known or referred to by a specific code name within an allied or cooperative context.
-
D.
alliedStatus
Indicates a relationship in which two or more entities are formally or informally aligned as allies, typically cooperating toward shared goals or mutual support.
-
E.
allianceDesignationSystem
Indicates a system that defines, assigns, or manages formal alliance designations between entities.
- F. None of above. chosen
Provenance (4 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c254e64881908f32f0d8144056df |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:53 a.m.