Triple
T31764509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 61 tank |
E810770
|
entity |
| Predicate | turretArmorType |
P172277
|
FINISHED |
| Object | cast steel |
—
|
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: cast steel | Statement: [Type 61 tank, turretArmorType, cast steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turretArmorType Context triple: [Type 61 tank, turretArmorType, cast steel]
-
A.
turret
Indicates that an entity is equipped with or associated with a turret, typically a rotating weapon or defense mechanism.
-
B.
hasTurretType
Indicates that one entity is equipped with or characterized by a specific type of turret.
-
C.
hasTurrets
Indicates that an entity is equipped with or possesses one or more turrets.
-
D.
turretBasedOn
Indicates that one turret is derived from, modeled after, or constructed using the design or components of another turret.
-
E.
turretDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a turret associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:31 p.m.