Triple
T7199815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Introductory Rites |
E168710
|
entity |
| Predicate | musicInvolved |
P69477
|
FINISHED |
| Object | Entrance hymn |
—
|
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: Entrance hymn | Statement: [Introductory Rites, musicInvolved, Entrance hymn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicInvolved Context triple: [Introductory Rites, musicInvolved, Entrance hymn]
-
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.
musicActivity
Indicates involvement in an activity related to creating, performing, practicing, or engaging with music.
-
C.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
D.
musicMovement
Indicates a relationship where a musical work, performance, or composition is associated with a specific movement or section within a larger musical piece.
-
E.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92cc8ac8190a6448b79496a8249 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.