Triple
T35116509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbé Birotteau |
E1013452
|
entity |
| Predicate | belongsToClergyRank |
P5046
|
FINISHED |
| Object | abbé |
—
|
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: abbé | Statement: [Abbé Birotteau, belongsToClergyRank, abbé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToClergyRank Context triple: [Abbé Birotteau, belongsToClergyRank, abbé]
-
A.
hasClergyRankOver
Indicates that one clergy member holds a higher ecclesiastical rank or authority than another within a religious hierarchy.
-
B.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
C.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
D.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
-
E.
ecclesiasticalRankRelative
Indicates a hierarchical relationship between two ecclesiastical positions, specifying which rank is higher, lower, or otherwise ordered relative to the other within a church structure.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4:01 p.m.