Triple
T32921776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emma Smith |
E842161
|
entity |
| Predicate | roleInChurchMusic |
P135541
|
FINISHED |
| Object | hymn compiler |
—
|
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: hymn compiler | Statement: [Emma Smith, roleInChurchMusic, hymn compiler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInChurchMusic Context triple: [Emma Smith, roleInChurchMusic, hymn compiler]
-
A.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
B.
roleInChurchProcess
Indicates that an entity holds a specific role or function within a defined church-related process or procedure.
-
C.
musicalEnsembleRole
chosen
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
-
D.
roleInSymphony
Indicates the specific function or part an entity performs within the context of a symphony.
-
E.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 1, 2026, 1:19 a.m.