Triple
T15630563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titular Archbishop of Belcastro |
E375799
|
entity |
| Predicate | hasSeeStatus |
P12717
|
FINISHED |
| Object | suppressed residential 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: suppressed residential diocese | Statement: [Titular Archbishop of Belcastro, hasSeeStatus, suppressed residential diocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeeStatus Context triple: [Titular Archbishop of Belcastro, hasSeeStatus, suppressed residential diocese]
-
A.
hasSee
Indicates that one entity has perceived or visually observed another entity.
-
B.
seeStatus
Indicates that one entity observes or becomes aware of the current state or condition of another entity or process.
-
C.
hasObserverStatusAt
Indicates that an entity holds observer status or role at a specified organization, event, or context.
-
D.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
E.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb536348190b93ed3c178d1ffb8 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.