Triple
T35749715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude Piéplu |
E1033282
|
entity |
| Predicate | hasNotableVoiceCharacteristic |
P156193
|
FINISHED |
| Object | dry, monotone delivery |
—
|
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: dry, monotone delivery | Statement: [Claude Piéplu, hasNotableVoiceCharacteristic, dry, monotone delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVoiceCharacteristic Context triple: [Claude Piéplu, hasNotableVoiceCharacteristic, dry, monotone delivery]
-
A.
hasNotableVocalFocus
Indicates that the subject is characterized by a particularly prominent or emphasized use of voice or vocals.
-
B.
hasDistinctiveVoice
Indicates that an entity possesses a voice that is notably unique or easily distinguishable from others.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
E.
hasVocalCharacter
chosen
Indicates that an entity possesses a particular vocal quality, style, or characteristic in its sound or voice.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.