Triple
T16444528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana-class battleship |
E399389
|
entity |
| Predicate | designedArmor |
P122814
|
FINISHED |
| Object | heavier than Iowa-class battleship |
—
|
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: heavier than Iowa-class battleship | Statement: [Montana-class battleship, designedArmor, heavier than Iowa-class battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedArmor Context triple: [Montana-class battleship, designedArmor, heavier than Iowa-class battleship]
-
A.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
B.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
C.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
-
D.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another entity.
-
E.
wearsArmor
Indicates that an entity is equipped with or dressed in armor as protective gear.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd9d474819091b4a80de1019c54 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.