Triple
T19811632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ka-52 |
E475959
|
entity |
| Predicate | hasHelmetMountedSight |
P137408
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ka-52, hasHelmetMountedSight, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHelmetMountedSight Context triple: [Ka-52, hasHelmetMountedSight, true]
-
A.
sightMounting
Indicates that an entity is equipped with or has a sighting device installed or mounted onto it.
-
B.
hasMuzzle
Indicates that one entity possesses or is equipped with a muzzle, typically as a restraining or protective device.
-
C.
hasNightVision
Indicates that an entity possesses the ability to see effectively in low-light or dark conditions.
-
D.
usedIronSights
Indicates that an entity performed an action or engaged in an activity by aiming through iron sights rather than using optical or electronic sights.
-
E.
helmetType
Indicates the specific category or style of helmet associated with an 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542c9c5c81908772e88caa067e63 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.