Triple
T3893732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I heard a Fly buzz—when I died |
E88120
|
entity |
| Predicate | usesSoundDevice |
P52711
|
FINISHED |
| Object | alliteration |
—
|
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: alliteration | Statement: [I heard a Fly buzz—when I died, usesSoundDevice, alliteration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSoundDevice Context triple: [I heard a Fly buzz—when I died, usesSoundDevice, alliteration]
-
A.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
soundHardware
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
C.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
D.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
E.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
- F. None of above. chosen
Provenance (4 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef1aada308190821a3dfa6af170b3 |
completed | March 9, 2026, 4:13 p.m. |
Created at: March 9, 2026, 3:21 p.m.