Triple
T23475758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caslon |
E570256
|
entity |
| Predicate | sloganOrSaying |
P116854
|
FINISHED |
| Object | When in doubt, use Caslon |
—
|
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: When in doubt, use Caslon | Statement: [Caslon, sloganOrSaying, When in doubt, use Caslon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganOrSaying Context triple: [Caslon, sloganOrSaying, When in doubt, use Caslon]
-
A.
sloganOrQuote
chosen
Indicates that one entity is a slogan or quoted phrase associated with another entity.
-
B.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
-
C.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
D.
coOccurringSlogan
Indicates that two slogans appear together within the same context, instance, or usage.
-
E.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a704e2a48190acb55f77a2124412 |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:01 p.m.