Triple
T2733378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opal |
E60368
|
entity |
| Predicate | hasTypicalTransparency |
P40821
|
FINISHED |
| Object | transparent to opaque |
—
|
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: transparent to opaque | Statement: [Opal, hasTypicalTransparency, transparent to opaque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTransparency Context triple: [Opal, hasTypicalTransparency, transparent to opaque]
-
A.
hasTransparencyRequirement
Indicates that one entity is obligated to provide clear, accessible information or disclosure to another entity or to the public.
-
B.
isTransparentTo
chosen
Indicates that one entity allows another entity (such as light, information, or influence) to pass through or be perceived without obstruction or concealment.
-
C.
transparency
Indicates that an entity’s internal processes, information, or decision-making are openly accessible and understandable to others.
-
D.
hasNanoTextureGlassOption
Indicates that an entity offers or includes an available option for nano-texture glass.
-
E.
hasClearance
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaf175808190acbbb3873c7c3f67 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.