Triple
T22430720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walbaum |
E554490
|
entity |
| Predicate | strokeContrast |
P108941
|
FINISHED |
| Object | strong stroke contrast |
—
|
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: strong stroke contrast | Statement: [Walbaum, strokeContrast, strong stroke contrast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strokeContrast Context triple: [Walbaum, strokeContrast, strong stroke contrast]
-
A.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
-
B.
textureContrast
chosen
Indicates a relationship where two surfaces or regions differ noticeably in their tactile or visual texture qualities.
-
C.
registerContrast
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
-
D.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
E.
tempoContrast
Indicates a relationship where two musical passages or sections differ in tempo, highlighting a contrast in their speed or pacing.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.