Triple
T22027023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIE standard illuminant D50 |
E543993
|
entity |
| Predicate | referenceMedium |
P146320
|
FINISHED |
| Object | daylight viewing booths |
—
|
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: daylight viewing booths | Statement: [CIE standard illuminant D50, referenceMedium, daylight viewing booths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceMedium Context triple: [CIE standard illuminant D50, referenceMedium, daylight viewing booths]
-
A.
targetMedium
Indicates the medium or channel through which an action, message, or effect is directed or intended to be delivered.
-
B.
canonicalMedium
Indicates the primary or standard medium through which something is most authoritatively or typically expressed, distributed, or experienced.
-
C.
repositoryMedium
Indicates the physical or digital medium through which a repository stores, maintains, or provides access to its contents.
-
D.
subjectMedium
Indicates the medium or channel through which the subject is expressed, communicated, or realized.
-
E.
informationMedium
Indicates the medium or channel through which information is conveyed or communicated between entities.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:24 p.m.