Triple
T6087837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Litany |
E135683
|
entity |
| Predicate | responseLanguageFormula |
P68577
|
FINISHED |
| Object | Kyrie eleison |
—
|
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: Kyrie eleison | Statement: [Little Litany, responseLanguageFormula, Kyrie eleison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseLanguageFormula Context triple: [Little Litany, responseLanguageFormula, Kyrie eleison]
-
A.
responseFormula
Indicates that one entity’s reaction, reply, or outcome is expressed or encoded in a specific formula or structured representation.
-
B.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
C.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
D.
公式言語
Indicates that something is expressed or represented using a formal language, typically defined by precise syntax and semantics.
-
E.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0578bf2508190859c2dbd4c10b316 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.