Triple
T28914625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevation Worship |
E733321
|
entity |
| Predicate | musicUsedIn |
P69477
|
FINISHED |
| Object | church services worldwide |
—
|
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: church services worldwide | Statement: [Elevation Worship, musicUsedIn, church services worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicUsedIn Context triple: [Elevation Worship, musicUsedIn, church services worldwide]
-
A.
musicUsed
chosen
Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
-
B.
musicMotif
Indicates a recurring musical idea, theme, or pattern that appears multiple times within a composition or across related works.
-
C.
usesMusicFor
Indicates that one entity employs or applies music as a means, tool, or resource to achieve or support some purpose, activity, or effect for another entity or context.
-
D.
musicComposedIn
Indicates that a piece of music was created or composed in a specific place or location.
-
E.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 8:13 a.m.