Triple
T28414705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EM-2 rifle |
E719768
|
entity |
| Predicate | sightMagnification |
P88977
|
FINISHED |
| Object | approximately 1.5× |
—
|
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: approximately 1.5× | Statement: [EM-2 rifle, sightMagnification, approximately 1.5×]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sightMagnification Context triple: [EM-2 rifle, sightMagnification, approximately 1.5×]
-
A.
typicalMagnification
Indicates the usual or characteristic degree to which something is enlarged or magnified under normal or standard conditions.
-
B.
sightMounting
Indicates that an entity is equipped with or has a sighting device installed or mounted onto it.
-
C.
viewfinderMagnification
chosen
Indicates the degree to which the viewfinder enlarges the scene relative to the naked eye.
-
D.
sightRadius
Indicates the maximum distance within which an entity can visually perceive or detect other entities or objects.
-
E.
M4EScope
Indicates that an entity’s scope, range, or applicability is defined or constrained within a specific M4E (Model for Evaluation) context.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:29 a.m.