Triple
T21750780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduals |
E536906
|
entity |
| Predicate | sungBetween |
P145227
|
FINISHED |
| Object | scripture readings |
—
|
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: scripture readings | Statement: [Graduals, sungBetween, scripture readings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sungBetween Context triple: [Graduals, sungBetween, scripture readings]
-
A.
concludedBetween
Indicates that an agreement, arrangement, or formal relationship has been finalized between two or more parties.
-
B.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
C.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
D.
runsBetween
Indicates a relationship where something extends, operates, or connects from one point, entity, or state to another along a path or interval.
-
E.
formedBetween
Indicates a relationship in which a connection, bond, or structure has come into existence linking two or more entities.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a79fb74819098a247c4f31598a8 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:50 p.m.