Triple
T38545327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel (mute version) |
E924948
|
entity |
| Predicate | voiceLostInExchangeFor |
P192697
|
FINISHED |
| Object | human legs |
—
|
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: human legs | Statement: [Ariel (mute version), voiceLostInExchangeFor, human legs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceLostInExchangeFor Context triple: [Ariel (mute version), voiceLostInExchangeFor, human legs]
-
A.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
B.
voiceDisorder
Indicates that an entity has a condition or impairment affecting the normal production, quality, or use of the voice.
-
C.
voiceInHeadOf
Indicates that one entity exists as an internal voice, thought, or auditory experience occurring within the mind of another entity.
-
D.
spokeVia
Indicates that communication or speech occurred through a particular medium, channel, or intermediary.
-
E.
hasVoicing
Indicates that one sound, segment, or phoneme is characterized by the presence or absence of vocal fold vibration (voicing) in relation to another or to a specified voicing property.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:32 p.m.