Triple
T23807059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misereatur prayer |
E589736
|
entity |
| Predicate | isSpokenAloud |
P80383
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Misereatur prayer, isSpokenAloud, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenAloud Context triple: [Misereatur prayer, isSpokenAloud, yes]
-
A.
isSpoken
chosen
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
B.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
C.
isSpokenAround
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
D.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
-
E.
spokenUntil
Indicates that an act of speaking or verbal communication continues up to a specific time or event and then stops.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c752ff6481908cfc20d4f178d526 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.