Triple
T28947020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangalacharan |
E730606
|
entity |
| Predicate | functionInRecital |
P171469
|
FINISHED |
| Object | to set spiritual tone |
—
|
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: to set spiritual tone | Statement: [Mangalacharan, functionInRecital, to set spiritual tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInRecital Context triple: [Mangalacharan, functionInRecital, to set spiritual tone]
-
A.
functionInOratorio
Indicates that one entity serves a specific function, role, or part within an oratorio.
-
B.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
C.
theatricalFunction
Indicates the role or purpose something serves within a theatrical context, such as its function in staging, performance, or dramatic presentation.
-
D.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
-
E.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
- F. None of above. chosen
Provenance (4 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 28, 2026, 8:41 a.m.