Triple
T31520440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mime |
E804191
|
entity |
| Predicate | canBeHeardIn |
P99033
|
FINISHED |
| Object | tenor voice type |
—
|
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: tenor voice type | Statement: [Mime, canBeHeardIn, tenor voice type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHeardIn Context triple: [Mime, canBeHeardIn, tenor voice type]
-
A.
isHeardIn
chosen
Indicates that a sound, voice, or audio from one entity is perceived or audible within the context, location, or medium of another entity.
-
B.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
C.
widelyRecordedIn
Indicates that an event, fact, or phenomenon has been documented or captured in many different records, sources, or media.
-
D.
spokenInNeighboringRegionsOf
Indicates that a language or speech variety is used in regions that geographically border the primary region associated with another language or entity.
-
E.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 30, 2026, 9:55 p.m.