Triple
T21025854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newman zip paintings |
E517939
|
entity |
| Predicate | zipDefinition |
P142514
|
FINISHED |
| Object | narrow vertical band of contrasting color |
—
|
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: narrow vertical band of contrasting color | Statement: [Newman zip paintings, zipDefinition, narrow vertical band of contrasting color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zipDefinition Context triple: [Newman zip paintings, zipDefinition, narrow vertical band of contrasting color]
-
A.
compressionType
Indicates the method or format used to compress data or content in the relationship.
-
B.
archiveFormat
Indicates the file format or type used to package or compress an archive.
-
C.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
D.
archiveContent
Indicates that content is being stored or moved into an archive state for long-term retention or historical reference.
-
E.
compressionCharacteristic
Indicates how an entity behaves or performs when subjected to compressive forces or pressure.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7c262c8190bceb8fd26be76983 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:55 p.m.