Triple
T25656546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sarod |
E643251
|
entity |
| Predicate | hasResonatorCover |
P188070
|
FINISHED |
| Object | animal skin |
—
|
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: animal skin | Statement: [sarod, hasResonatorCover, animal skin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResonatorCover Context triple: [sarod, hasResonatorCover, animal skin]
-
A.
hasSpinCover
Indicates that one space or manifold serves as a spin cover of another, providing a covering map that lifts its structure to a spin structure.
-
B.
hasSoundHole
Indicates that one entity possesses or features a sound hole as a characteristic or component.
-
C.
isResonance
Indicates that one entity vibrates or responds in harmony with another, typically amplifying or reinforcing its effect or signal.
-
D.
hasOpenCoverCondition
Indicates that a mathematical object satisfies the open cover condition, meaning every open cover of it admits a suitable refinement or subcover meeting the specified requirement.
-
E.
hasTouchCoverCompatibility
Indicates that one entity is compatible for use with a specific touch cover accessory associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 21, 2026, 6:34 p.m.