Triple
T1254487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass of St. Pius V |
E26955
|
entity |
| Predicate | primaryOrientation |
P1101
|
FINISHED |
| Object | ad orientem |
—
|
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: ad orientem | Statement: [Mass of St. Pius V, primaryOrientation, ad orientem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOrientation Context triple: [Mass of St. Pius V, primaryOrientation, ad orientem]
-
A.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
B.
primaryAlignment
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
-
C.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
D.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa5a4cc819093ed686619b572d8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.