Triple
T31106803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodan (MonsterVerse) |
E792814
|
entity |
| Predicate | voiceAndRoarDesignBy |
P32563
|
FINISHED |
| Object | Erik Aadahl |
E1564053
|
NE 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: Erik Aadahl | Statement: [Rodan (MonsterVerse), voiceAndRoarDesignBy, Erik Aadahl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceAndRoarDesignBy Context triple: [Rodan (MonsterVerse), voiceAndRoarDesignBy, Erik Aadahl]
-
A.
soundDesignBy
chosen
Indicates that the sound design for a work (such as a film, game, or performance) is created or supervised by a particular person or entity.
-
B.
canRoar
Indicates that one entity has the ability to produce a roar, typically a loud, deep vocalization.
-
C.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
D.
voiceTypeOfOroe
Indicates that an entity represents the specific type or classification of voice associated with Oroe.
-
E.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
- F. None of above.
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a71f0352c8190ba9e595320b4a32c |
completed | June 11, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:03 p.m.