Triple
T24235154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Cochran |
E601853
|
entity |
| Predicate | settingContrast |
P40635
|
FINISHED |
| Object | small-town church choir |
—
|
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: small-town church choir | Statement: [Arthur Cochran, settingContrast, small-town church choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingContrast Context triple: [Arthur Cochran, settingContrast, small-town church choir]
-
A.
textureContrast
Indicates a relationship where two surfaces or regions differ noticeably in their tactile or visual texture qualities.
-
B.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
-
C.
tempoContrast
Indicates a relationship where two musical passages or sections differ in tempo, highlighting a contrast in their speed or pacing.
-
D.
registerContrast
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
-
E.
createsContrastIn
chosen
Indicates a relationship where one element is used to highlight or emphasize differences with another element within a given context.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9a4b708190851504c302778fd2 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.