Triple
T1087028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Litany |
E24075
|
entity |
| Predicate | typicalPositionInService |
P5188
|
FINISHED |
| Object | beginning of the Divine Liturgy |
—
|
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: beginning of the Divine Liturgy | Statement: [Great Litany, typicalPositionInService, beginning of the Divine Liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPositionInService Context triple: [Great Litany, typicalPositionInService, beginning of the Divine Liturgy]
-
A.
typicalPilotPosition
Indicates the usual or standard spatial position or placement where a pilot is located relative to the associated object or system.
-
B.
typicalPositionBias
Indicates a systematic tendency for something to be placed, chosen, or interpreted in a commonly favored or default position relative to other options.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
positionInWork
chosen
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b963161081908a523c8d63871652 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.