Triple
T17260076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M10 tank destroyer |
E418985
|
entity |
| Predicate | hasArmorLayout |
P93507
|
FINISHED |
| Object | sloped armor |
—
|
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: sloped armor | Statement: [M10 tank destroyer, hasArmorLayout, sloped armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArmorLayout Context triple: [M10 tank destroyer, hasArmorLayout, sloped armor]
-
A.
armourLayout
chosen
Indicates how pieces of armour are arranged or distributed relative to each other or to a subject.
-
B.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
-
C.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
D.
armourCoverage
Indicates the extent or area of a subject’s body or structure that is protected or covered by armour.
-
E.
designedArmor
Indicates that one entity created or planned the armor used or worn by another 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6fa940819089046d1b12dede2c |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.