Triple
T2011624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerald |
E43698
|
entity |
| Predicate | transparency |
P34462
|
FINISHED |
| Object | Transparent to translucent |
—
|
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 translucent | Statement: [Emerald, transparency, Transparent to translucent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transparency Context triple: [Emerald, transparency, Transparent to translucent]
-
A.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
B.
hasTransparencyRequirement
Indicates that one entity is obligated to provide clear, accessible information or disclosure to another entity or to the public.
-
C.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
D.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
E.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b150a8819096c919465fd91ab5 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:37 p.m.