Triple
T6578550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Indomitable |
E157232
|
entity |
| Predicate | armourFeature |
P32307
|
FINISHED |
| Object | armoured flight deck |
—
|
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: armoured flight deck | Statement: [HMS Indomitable, armourFeature, armoured flight deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armourFeature Context triple: [HMS Indomitable, armourFeature, armoured flight deck]
-
A.
armorFeature
chosen
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
B.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
C.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
D.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
-
E.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.