Triple
T4737221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FV101 Scorpion |
E105153
|
entity |
| Predicate | armorLayout |
P32307
|
FINISHED |
| Object | welded aluminium hull |
—
|
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: welded aluminium hull | Statement: [FV101 Scorpion, armorLayout, welded aluminium hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armorLayout Context triple: [FV101 Scorpion, armorLayout, welded aluminium hull]
-
A.
armorFeature
chosen
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
B.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
C.
armorBelt
Indicates that an entity is equipped with or wearing an armor belt as part of its protective gear.
-
D.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
E.
armourBelt
Indicates a relationship where an armour belt is equipped on, attached to, or associated with an entity (such as a character, vehicle, or structure) as protective gear.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64844b7081909c9d36e4b461379e |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.