Triple
T30644192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 50mm f/1.2 GM |
E780073
|
entity |
| Predicate | weatherSealed |
P170263
|
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 50mm f/1.2 GM, weatherSealed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weatherSealed Context triple: [Sony FE 50mm f/1.2 GM, weatherSealed, yes]
-
A.
upperDeckUsedFor
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
B.
cardPackAvailableIn
Indicates that a particular card pack can be obtained, accessed, or used within a specified context, location, or platform.
-
C.
hasFoilOrParallel
Indicates that one item is a foil or parallel version of another, typically differing only in special variant features while representing the same underlying entity.
-
D.
iconicTCGCard
Indicates that a trading card game (TCG) card is widely recognized as emblematic or highly representative of its game or format.
-
E.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 29, 2026, 8:29 p.m.