Triple
T17635707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark I tank |
E430086
|
entity |
| Predicate | primaryArmour |
P11885
|
FINISHED |
| Object | riveted steel plate |
—
|
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: riveted steel plate | Statement: [Mark I tank, primaryArmour, riveted steel plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArmour Context triple: [Mark I tank, primaryArmour, riveted steel plate]
-
A.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
B.
armorType
chosen
Indicates the specific category or classification of protective armor associated with an entity.
-
C.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
D.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
E.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de0ad988190b1a2c0bff69eb9f1 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.