Triple
T22850771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kartal (cymbals) |
E566348
|
entity |
| Predicate | usedInPerformanceType |
P25490
|
FINISHED |
| Object | congregational singing |
—
|
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: congregational singing | Statement: [Kartal (cymbals), usedInPerformanceType, congregational singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInPerformanceType Context triple: [Kartal (cymbals), usedInPerformanceType, congregational singing]
-
A.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
performanceUse
Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
-
C.
usedInMatchType
Indicates that something (such as a rule, item, or configuration) is applied or relevant within a specific type or category of match.
-
D.
intendedForPerformanceBy
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
-
E.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.