Triple
T12818863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhodopian bagpipe |
E306473
|
entity |
| Predicate | hornUsage |
P2529
|
FINISHED |
| Object | often uses animal horn on chanter end |
—
|
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: often uses animal horn on chanter end | Statement: [Rhodopian bagpipe, hornUsage, often uses animal horn on chanter end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornUsage Context triple: [Rhodopian bagpipe, hornUsage, often uses animal horn on chanter end]
-
A.
hornInterpretedAs
Indicates that one entity’s horn is understood, interpreted, or taken to represent another entity or concept.
-
B.
hornCount
Indicates the number of horns possessed by an entity.
-
C.
hornSheath
Indicates that one entity is the protective outer covering or sheath surrounding the horn of another entity.
-
D.
hammerRepresents
Indicates that one entity serves as a symbolic or representative depiction of a hammer in relation to another entity.
-
E.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9d00088190ac0f5d60e1de7a7c |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.