Triple
T36169008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M18 Hellcat |
E1046094
|
entity |
| Predicate | armoredProtection |
P92616
|
FINISHED |
| Object | thin armor to reduce weight |
—
|
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: thin armor to reduce weight | Statement: [M18 Hellcat, armoredProtection, thin armor to reduce weight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armoredProtection Context triple: [M18 Hellcat, armoredProtection, thin armor to reduce weight]
-
A.
armourProtection
Indicates that one entity provides protective armor or defensive covering for another entity.
-
B.
hasArmorPlating
Indicates that one entity is equipped with or covered by protective armor plating in relation to another entity or context.
-
C.
armored
chosen
Indicates that an entity is protected by armor or a defensive covering against damage or attack.
-
D.
armorProtectionLevel
Indicates the degree or rating of protective capability that armor provides against threats or damage.
-
E.
armourCoverage
Indicates the extent or area of a subject’s body or structure that is protected or covered by armour.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.