Triple
T2662606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Archdiocese of Utrecht |
E54758
|
entity |
| Predicate | typeOfOrdinary |
P5518
|
FINISHED |
| Object | Residential archbishop |
—
|
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: Residential archbishop | Statement: [Roman Catholic Archdiocese of Utrecht, typeOfOrdinary, Residential archbishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOrdinary Context triple: [Roman Catholic Archdiocese of Utrecht, typeOfOrdinary, Residential archbishop]
-
A.
oreType
Indicates the specific kind or classification of ore associated with an entity.
-
B.
currentOrdinary
Indicates that an entity currently holds or is in the state of an ordinary (non-special or non-exceptional) status or role.
-
C.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
D.
typeOfPrimacy
Indicates that one entity holds a primary, leading, or most important status or precedence over others in a given context.
-
E.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd969eff08190a206ad6424ba34d6 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.