Triple
T38545325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel (mute version) |
E924948
|
entity |
| Predicate | causeOfMutism |
P694
|
FINISHED |
| Object | loss of voice |
—
|
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: loss of voice | Statement: [Ariel (mute version), causeOfMutism, loss of voice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfMutism Context triple: [Ariel (mute version), causeOfMutism, loss of voice]
-
A.
overcomesMutismWith
Indicates that one entity helps another entity to successfully overcome or recover from a condition of mutism.
-
B.
causeOfVow
Indicates that one event, condition, or entity is the reason or motivating factor behind another entity making a vow.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
cannotBeEasilySpokenBy
Indicates that one entity (typically a word, phrase, or name) is difficult for another entity (typically a speaker or group) to pronounce or articulate smoothly.
-
E.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:32 p.m.