Triple
T1097125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin West |
E24294
|
entity |
| Predicate | dominantRite |
P23108
|
FINISHED |
| Object | Latin rite |
—
|
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: Latin rite | Statement: [Latin West, dominantRite, Latin rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantRite Context triple: [Latin West, dominantRite, Latin rite]
-
A.
notableRite
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
-
B.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
-
C.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
D.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
E.
religiousAdministration
Indicates that one entity holds authority or responsibility for managing, overseeing, or governing the religious affairs, practices, or institutions of another entity.
- F. None of above. chosen
Provenance (4 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9a1d3108190b2a304fef429848d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.