Triple
T3129406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tical |
E65372
|
entity |
| Predicate | soundCharacterization |
P8089
|
FINISHED |
| Object | gritty |
—
|
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: gritty | Statement: [Tical, soundCharacterization, gritty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundCharacterization Context triple: [Tical, soundCharacterization, gritty]
-
A.
soundCharacter
chosen
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
-
B.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
C.
speakerFeatures
Indicates that certain characteristics, attributes, or properties are associated with a speaker in a given context.
-
D.
signatureSound
Indicates that something has a distinctive, characteristic sound that uniquely identifies it.
-
E.
acousticProperty
Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada549aaa881908dcf92d20fa6f238 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.