Triple
T16098558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squiggy |
E390550
|
entity |
| Predicate | typicalSpeechStyle |
P35511
|
FINISHED |
| Object | nasal tone |
—
|
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: nasal tone | Statement: [Squiggy, typicalSpeechStyle, nasal tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeechStyle Context triple: [Squiggy, typicalSpeechStyle, nasal tone]
-
A.
typicalDialogueStyle
Indicates the characteristic manner or pattern in which an entity typically communicates or conducts dialogue.
-
B.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
C.
typicalLanguageUse
Indicates that one entity is the language most commonly or habitually used by another entity in ordinary communication or contexts.
-
D.
speechType
Indicates the specific category or form of spoken or written communication that an utterance or speech act belongs to (e.g., question, statement, command).
-
E.
rhetoricalStyle
chosen
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6672848190922b5ebb90e18947 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.