Triple
T30532302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 24mm f/1.4 GM |
E777037
|
entity |
| Predicate | hasCustomButton |
P92562
|
FINISHED |
| Object | focus hold button |
—
|
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: focus hold button | Statement: [Sony FE 24mm f/1.4 GM, hasCustomButton, focus hold button]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomButton Context triple: [Sony FE 24mm f/1.4 GM, hasCustomButton, focus hold button]
-
A.
hasButtons
chosen
Indicates that an entity possesses one or more buttons as part of its features or design.
-
B.
haveCustom
Indicates that one entity possesses, uses, or is associated with a non-standard or specially tailored version of another entity.
-
C.
hasHomeButton
Indicates that an entity possesses or includes a physical or virtual home button.
-
D.
hasOnboardButton
Indicates that one entity is equipped with or includes a button installed on or within it.
-
E.
hasResetButton
Indicates that an entity is equipped with a reset button that can restore it to a default or initial state.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 29, 2026, 8:18 p.m.