Triple
T30358543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 200-600mm f/5.6-6.3 G OSS |
E772209
|
entity |
| Predicate | tripodMount |
P169104
|
FINISHED |
| Object | removable rotating tripod collar |
—
|
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: removable rotating tripod collar | Statement: [Sony FE 200-600mm f/5.6-6.3 G OSS, tripodMount, removable rotating tripod collar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tripodMount Context triple: [Sony FE 200-600mm f/5.6-6.3 G OSS, tripodMount, removable rotating tripod collar]
-
A.
bipod
Indicates that an entity is supported or stabilized by a two-legged stand or support structure.
-
B.
trainMounting
Indicates a relationship where an entity is boarding or getting onto a train.
-
C.
telescopeMountedOn
Indicates that a telescope is physically installed or fixed onto a specific supporting structure or platform.
-
D.
telescopeMountType
Indicates the type of mounting mechanism used to support and orient a telescope.
-
E.
usesLensMount
Indicates that one device or component is designed to accept, attach to, or operate with a specific type of lens mount.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682417ec08190982dd9acf7219742 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:57 p.m.