Triple
T9502563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α1 |
E229179
|
entity |
| Predicate | weatherSealing |
P20750
|
FINISHED |
| Object | dust and moisture resistant |
—
|
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: dust and moisture resistant | Statement: [Sony α1, weatherSealing, dust and moisture resistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weatherSealing Context triple: [Sony α1, weatherSealing, dust and moisture resistant]
-
A.
waterResistanceRating
Indicates the level to which something can resist water penetration or damage under specified conditions.
-
B.
designedToWithstand
chosen
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
C.
protectsProductType
Indicates that one entity provides protection or safeguarding specifically for a certain type or category of product.
-
D.
waterTolerance
Indicates the degree to which an entity can withstand or function effectively in the presence of water.
-
E.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983ea6048190a2d7924c8e6d1fbc |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.