Triple
T36592868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Oriens |
E902715
|
entity |
| Predicate | chronologicalOrderInOAntiphons |
P197184
|
FINISHED |
| Object | fifth |
—
|
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: fifth | Statement: [O Oriens, chronologicalOrderInOAntiphons, fifth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderInOAntiphons Context triple: [O Oriens, chronologicalOrderInOAntiphons, fifth]
-
A.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
B.
liturgicalSequence
Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
chronologicalOrderInGospels
Indicates that the events or elements are arranged in the sequence in which they occur within the Gospel narratives.
-
E.
chronologicalOrderOfGospels
Indicates the temporal sequence in which the Gospels are believed or asserted to have been written or occurred relative to one another.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:11 p.m.