Triple
T934977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glorious Mysteries |
E20174
|
entity |
| Predicate | sequencePosition |
P11426
|
FINISHED |
| Object | third set of Rosary mysteries |
—
|
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: third set of Rosary mysteries | Statement: [Glorious Mysteries, sequencePosition, third set of Rosary mysteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequencePosition Context triple: [Glorious Mysteries, sequencePosition, third set of Rosary mysteries]
-
A.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
-
B.
chainPosition
chosen
Indicates the position or rank an entity occupies within an ordered chain or sequence relative to other entities.
-
C.
discPosition
Indicates the spatial or ordinal placement of a disc relative to a reference point or within a set or structure.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.