Triple
T30382277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony E |
E772862
|
entity |
| Predicate | canMountOn |
P166525
|
FINISHED |
| Object | Sony full-frame E-mount cameras with crop mode |
—
|
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: Sony full-frame E-mount cameras with crop mode | Statement: [Sony E, canMountOn, Sony full-frame E-mount cameras with crop mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canMountOn Context triple: [Sony E, canMountOn, Sony full-frame E-mount cameras with crop mode]
-
A.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
B.
mountableIn
chosen
Indicates that one entity can be mounted, installed, or attached within or onto another entity.
-
C.
mountableBy
Indicates that one entity can be physically mounted, ridden, or climbed upon by another entity.
-
D.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
E.
trainMounting
Indicates a relationship where an entity is boarding or getting onto a train.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6851aeb948190b674200cf6bf51f9 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8 p.m.