Triple
T7556650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado-class battleship |
E178682
|
entity |
| Predicate | armoredWith |
P11885
|
FINISHED |
| Object | belt armor up to about 13.5 inches |
—
|
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: belt armor up to about 13.5 inches | Statement: [Colorado-class battleship, armoredWith, belt armor up to about 13.5 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armoredWith Context triple: [Colorado-class battleship, armoredWith, belt armor up to about 13.5 inches]
-
A.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
B.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another entity.
-
C.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
D.
armorFeature
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
E.
armorType
chosen
Indicates the specific category or classification of protective armor associated with an 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8d9ebe48190a08110695ce1eb55 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.