Triple
T1005820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastmancolor |
E21707
|
entity |
| Predicate | archivalConcern |
P21735
|
FINISHED |
| Object | color fading over time |
—
|
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: color fading over time | Statement: [Eastmancolor, archivalConcern, color fading over time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivalConcern Context triple: [Eastmancolor, archivalConcern, color fading over time]
-
A.
archivesHeldIn
Indicates that archival materials or records are stored, maintained, or preserved at a specified location or institution.
-
B.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
-
C.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
D.
aimsToPreserve
Indicates an intention or effort by one entity to maintain, protect, or keep another entity in its current or desired state.
-
E.
notableReaccession
Indicates a significant or noteworthy instance of something being reacquired, reaccepted, or readmitted after having previously left or been removed.
- 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_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. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:41 p.m.