Triple
T26802348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columban church |
E671133
|
entity |
| Predicate | ecclesiasticalPractice |
P128075
|
FINISHED |
| Object | distinct tonsure |
—
|
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: distinct tonsure | Statement: [Columban church, ecclesiasticalPractice, distinct tonsure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecclesiasticalPractice Context triple: [Columban church, ecclesiasticalPractice, distinct tonsure]
-
A.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
-
B.
ecclesialUse
Indicates that something is used, practiced, or applied within an ecclesial (church or religious institutional) context.
-
C.
ecclesiasticalPolity
Indicates the form, structure, and governing system by which a religious or church organization is administered and its authority is distributed.
-
D.
ritualChurch
chosen
Indicates a relationship where a ritual is formally associated with, performed within, or prescribed by a church or church institution.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 4:24 a.m.