Triple
T4904843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crowning with Thorns |
E109889
|
entity |
| Predicate | hasPositionInSeries |
P33773
|
FINISHED |
| Object | third Sorrowful Mystery of the Rosary |
—
|
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 Sorrowful Mystery of the Rosary | Statement: [Crowning with Thorns, hasPositionInSeries, third Sorrowful Mystery of the Rosary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInSeries Context triple: [Crowning with Thorns, hasPositionInSeries, third Sorrowful Mystery of the Rosary]
-
A.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
B.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
C.
hasAssociatedPosition
Indicates that one entity is linked to a specific role, job, or spatial/organizational position associated with it.
-
D.
positionInSet
chosen
Indicates that an entity occupies a specific position or rank within an ordered set or collection.
-
E.
hasUniquePositionWithin
Indicates that an entity occupies a distinct, non-shared position or role within a specified context or collection.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.