Triple
T897529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha |
E19376
|
entity |
| Predicate | representsSound |
P8089
|
FINISHED |
| Object | open front unrounded vowel |
—
|
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: open front unrounded vowel | Statement: [Alpha, representsSound, open front unrounded vowel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsSound Context triple: [Alpha, representsSound, open front unrounded vowel]
-
A.
signatureSound
Indicates that something has a distinctive, characteristic sound that uniquely identifies it.
-
B.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
-
C.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
-
D.
soundCarrier
Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
-
E.
soundCharacter
chosen
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9635608190a297e2067b8dcee2 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.