Triple
T36515233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington-class battlecruiser |
E900016
|
entity |
| Predicate | designedArmorType |
P122814
|
FINISHED |
| Object | battlecruiser-style protection |
—
|
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: battlecruiser-style protection | Statement: [Lexington-class battlecruiser, designedArmorType, battlecruiser-style protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedArmorType Context triple: [Lexington-class battlecruiser, designedArmorType, battlecruiser-style protection]
-
A.
designedArmor
chosen
Indicates that one entity created or planned the armor used or worn by another entity.
-
B.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
C.
legArmorType
Indicates the specific category or kind of protective covering worn on the legs.
-
D.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
E.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:10 p.m.