Triple
T12604918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel acclamation |
E300952
|
entity |
| Predicate | positionInOrderOfMass |
P37518
|
FINISHED |
| Object | between the Second Reading and the Gospel |
—
|
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: between the Second Reading and the Gospel | Statement: [Gospel acclamation, positionInOrderOfMass, between the Second Reading and the Gospel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInOrderOfMass Context triple: [Gospel acclamation, positionInOrderOfMass, between the Second Reading and the Gospel]
-
A.
positionInMass
Indicates that an entity occupies a specific location or role within a larger undifferentiated group, collection, or mass.
-
B.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
rankByMassInAsteroidBelt
Indicates the relative ordering of objects in the asteroid belt based on their mass, from most massive to least massive (or vice versa).
-
D.
movementOrderedBy
Indicates that one entity’s movement occurs according to, or is arranged/controlled by, another entity’s ordering or directive.
-
E.
placedInOrderBy
Indicates that one entity was arranged or positioned according to a sequence or priority determined by 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:10 p.m.