Triple
T1005810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastmancolor |
E21707
|
entity |
| Predicate | componentLayers |
P14071
|
FINISHED |
| Object | red-sensitive layer |
—
|
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: red-sensitive layer | Statement: [Eastmancolor, componentLayers, red-sensitive layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentLayers Context triple: [Eastmancolor, componentLayers, red-sensitive layer]
-
A.
operationalLayer
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
B.
concernsLayer
Indicates that something is related or pertains specifically to a particular layer within a layered structure or system.
-
C.
component1
chosen
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
D.
germLayers
Indicates the developmental relationship between an organism or structure and the embryonic germ layers (ectoderm, mesoderm, endoderm) from which it originates.
-
E.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b51303548190a5ee3c0797fc3245 |
completed | March 1, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b2e7108190b338b6c19d4aff55 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.