Triple
T31152101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Meany |
E794101
|
entity |
| Predicate | hasMannerOfSpeech |
P156142
|
FINISHED |
| Object | high-pitched gravelly tone |
—
|
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: high-pitched gravelly tone | Statement: [Owen Meany, hasMannerOfSpeech, high-pitched gravelly tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMannerOfSpeech Context triple: [Owen Meany, hasMannerOfSpeech, high-pitched gravelly tone]
-
A.
hasModeOfSpeech
chosen
Indicates the manner or style in which an entity expresses itself verbally or communicates through speech.
-
B.
hasManner
Indicates the way, style, or method in which an action is performed or a relation is carried out.
-
C.
hasSpeakingStyle
Indicates that one entity exhibits or is characterized by a particular manner or style of speaking in relation to another entity.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
hasSpeechMode
Indicates that an entity is associated with, or operates using, a particular mode or style of speech or vocal communication.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
Created at: April 29, 2026, 9:06 p.m.