Triple
T30698727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 100-400mm f/4.5-5.6 GM OSS |
E781549
|
entity |
| Predicate | AFLimiterSwitch |
P34291
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sony FE 100-400mm f/4.5-5.6 GM OSS, AFLimiterSwitch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AFLimiterSwitch Context triple: [Sony FE 100-400mm f/4.5-5.6 GM OSS, AFLimiterSwitch, yes]
-
A.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
hasOnboardSwitch
chosen
Indicates that one entity is equipped with a built-in switch located on or within it.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
switchOnBy
Indicates that an entity is turned on or activated as the result of an action performed by another entity.
-
E.
hasAutomaticTrainControlCompatibility
Indicates that an entity is compatible with, or supports integration with, an automatic train control (ATC) system.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68bdceb8c8190b78e499ea2357e0f |
completed | May 2, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:34 p.m.