Triple
T37460383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaddius |
E930901
|
entity |
| Predicate | voiceLine |
P77440
|
FINISHED |
| Object | You are too late... I... must... obey! |
—
|
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: You are too late... I... must... obey! | Statement: [Thaddius, voiceLine, You are too late... I... must... obey!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceLine Context triple: [Thaddius, voiceLine, You are too late... I... must... obey!]
-
A.
voiceWork
Indicates that one entity performs or contributes voice acting or vocal performance work for another entity or creative production.
-
B.
dialogueLine
chosen
Indicates that one entity is a specific spoken or written line of dialogue expressed by another entity (such as a character or speaker).
-
C.
voiceCharacter
Indicates that one entity provides the voice for, or vocally portrays, a particular character in a work.
-
D.
voiceActingLanguage
Indicates the language in which a voice acting performance is delivered.
-
E.
voiceAppearance
Indicates that one entity’s voice is present, heard, or featured in association with another entity (such as a work, scene, or medium).
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.