Triple
T17290719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS-1 |
E419775
|
entity |
| Predicate | turretMount |
P57777
|
FINISHED |
| Object | 85 mm gun turret |
—
|
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: 85 mm gun turret | Statement: [IS-1, turretMount, 85 mm gun turret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turretMount Context triple: [IS-1, turretMount, 85 mm gun turret]
-
A.
turret
Indicates that an entity is equipped with or associated with a turret, typically a rotating weapon or defense mechanism.
-
B.
weaponMount
chosen
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
C.
turretPlacement
Indicates the spatial or positional relationship defining where a turret is placed relative to its environment or reference objects.
-
D.
typeOfGunMount
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
E.
turretBasedOn
Indicates that one turret is derived from, modeled after, or constructed using the design or components of another turret.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437837d048190949b947f5437636d |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.