Triple
T15156891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaplinsky v. New Hampshire |
E362101
|
entity |
| Predicate | speechCategory |
P29536
|
FINISHED |
| Object | unprotected speech |
—
|
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: unprotected speech | Statement: [Chaplinsky v. New Hampshire, speechCategory, unprotected speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speechCategory Context triple: [Chaplinsky v. New Hampshire, speechCategory, unprotected speech]
-
A.
speechType
chosen
Indicates the specific category or form of spoken or written communication that an utterance or speech act belongs to (e.g., question, statement, command).
-
B.
speakerType
Indicates the role or category of a participant in a communicative act (e.g., narrator, quoted speaker, system voice) within a given context.
-
C.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
-
D.
typeOfSpeechDelivered
Indicates that a specific kind or category of speech (e.g., keynote, lecture, toast) was delivered in a given event or context.
-
E.
speechAlsoKnownAs
Indicates that a speech or spoken work is referred to by an alternative name, title, or alias.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060c62b08190bcdbd912d011d1ba |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.