Triple
T15817406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retvizan |
E383513
|
entity |
| Predicate | armoredType |
P11885
|
FINISHED |
| Object | belt-armored 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: belt-armored battleship | Statement: [Retvizan, armoredType, belt-armored battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armoredType Context triple: [Retvizan, armoredType, belt-armored battleship]
-
A.
armored
Indicates that an entity is protected by armor or a defensive covering against damage or attack.
-
B.
armorType
chosen
Indicates the specific category or classification of protective armor associated with an entity.
-
C.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
D.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
-
E.
armoredBeltThickness
Indicates the thickness of an entity’s protective armored belt in the context of its defensive structure or design.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a4332c8190bc525e06d6f3a6b4 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.