Triple
T22875049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathismata |
E567299
|
entity |
| Predicate | exceptionToPosture |
P13260
|
FINISHED |
| Object | Glory be doxology often said standing |
—
|
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: Glory be doxology often said standing | Statement: [Kathismata, exceptionToPosture, Glory be doxology often said standing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exceptionToPosture Context triple: [Kathismata, exceptionToPosture, Glory be doxology often said standing]
-
A.
exceptionToOaths
Indicates that a situation, condition, or rule provides a valid exception to an otherwise binding oath or sworn obligation.
-
B.
exception
chosen
Indicates that a particular case does not follow the usual rule, pattern, or condition that applies to others.
-
C.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
D.
throwsPosition
Indicates that one entity performs a throwing action that determines or affects the spatial position of another entity.
-
E.
statesExceptionFor
Indicates that one entity formally specifies an exception or exclusion that applies to another entity or rule.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f57a1ec8190b8c6a0080d97a2a2 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:39 p.m.