Triple
T28310488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG36 |
E713978
|
entity |
| Predicate | usesSights |
P45300
|
FINISHED |
| Object | optical sight (G36-style carry handle optic) |
—
|
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: optical sight (G36-style carry handle optic) | Statement: [MG36, usesSights, optical sight (G36-style carry handle optic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSights Context triple: [MG36, usesSights, optical sight (G36-style carry handle optic)]
-
A.
hasSights
chosen
Indicates that an entity possesses or features notable sights, attractions, or points of interest.
-
B.
sights
Indicates that one entity perceives or observes another entity or object using vision.
-
C.
typicalSights
Indicates that certain sights or visual features are commonly or characteristically observed in association with a given entity or context.
-
D.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
E.
sightType
Indicates the specific kind or category of sight or visual perception associated with an entity or event.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 11:40 p.m.