Triple
T6388150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novus Ordo |
E143751
|
entity |
| Predicate | celebratedVersus |
P37303
|
FINISHED |
| Object | versus populum |
—
|
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: versus populum | Statement: [Novus Ordo, celebratedVersus, versus populum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebratedVersus Context triple: [Novus Ordo, celebratedVersus, versus populum]
-
A.
celebratedInForm
chosen
Indicates that something is honored, observed, or commemorated through a particular medium, style, or manner of expression.
-
B.
isCelebratedWith
Indicates that an event, occasion, or person is marked or honored using a particular method, activity, or accompanying element (e.g., a party, ritual, or object).
-
C.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
D.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
E.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686b4f34819088ff07185b34e536 |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.