Triple
T34477453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Moulins |
E885077
|
entity |
| Predicate | partOfHierarchyLevel |
P59179
|
FINISHED |
| Object | suffragan diocese |
—
|
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: suffragan diocese | Statement: [Diocese of Moulins, partOfHierarchyLevel, suffragan diocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHierarchyLevel Context triple: [Diocese of Moulins, partOfHierarchyLevel, suffragan diocese]
-
A.
isPartOfHierarchyWith
Indicates that one entity occupies a defined position within an ordered or nested structure relative to another entity in the same hierarchy.
-
B.
hierarchyLevelCode
Indicates the specific rank or position an entity holds within a defined hierarchy or organizational structure.
-
C.
partOfTier
chosen
Indicates that one entity belongs to, is included within, or forms a component of a specified tier or level in a hierarchical structure.
-
D.
levelInAdministrativeHierarchy
Indicates the relative position or rank of an administrative unit within a broader hierarchical administrative structure.
-
E.
partyHierarchyRank
Indicates the relative position or level of an entity within an ordered party hierarchy.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: May 1, 2026, 2:01 a.m.