Triple
T16279166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chick Hicks |
E395217
|
entity |
| Predicate | voiceTypeDescription |
P2000
|
FINISHED |
| Object | loud and overconfident |
—
|
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: loud and overconfident | Statement: [Chick Hicks, voiceTypeDescription, loud and overconfident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceTypeDescription Context triple: [Chick Hicks, voiceTypeDescription, loud and overconfident]
-
A.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
voiceAppearance
Indicates that one entity’s voice is present, heard, or featured in association with another entity (such as a work, scene, or medium).
-
C.
speakerType
Indicates the role or category of a participant in a communicative act (e.g., narrator, quoted speaker, system voice) within a given context.
-
D.
voiceActingType
Indicates the specific style or category of voice performance used in an audio-visual work or production.
-
E.
speakerFeatures
Indicates that certain characteristics, attributes, or properties are associated with a speaker in 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24610908c8190921e507dcb4d8250 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.