Triple
T37616567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | engalabi drum |
E935939
|
entity |
| Predicate | typicalPitch |
P49771
|
FINISHED |
| Object | high-pitched |
—
|
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 | Statement: [engalabi drum, typicalPitch, high-pitched]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPitch Context triple: [engalabi drum, typicalPitch, high-pitched]
-
A.
typicalTimbre
Indicates that an entity has the characteristic or standard sound quality (timbre) that is typical or expected for its kind.
-
B.
pitchDeterminedBy
Indicates that the pitch of one entity is defined or controlled by another specified factor or entity.
-
C.
hasPitch
chosen
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
D.
relativePitch
Indicates a relationship where one entity’s pitch is defined or compared in terms of its interval or distance from another entity’s pitch.
-
E.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.