Triple
T32478609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Dili |
E830045
|
entity |
| Predicate | establishedAsDioceseOn |
P132442
|
FINISHED |
| Object | 1940-11-30 |
—
|
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: 1940-11-30 | Statement: [Roman Catholic Diocese of Dili, establishedAsDioceseOn, 1940-11-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsDioceseOn Context triple: [Roman Catholic Diocese of Dili, establishedAsDioceseOn, 1940-11-30]
-
A.
establishedAsArchdioceseOn
Indicates that a religious jurisdiction was formally elevated to the status of an archdiocese on a specific date.
-
B.
dioceseErectedOn
chosen
Indicates the date or point in time when a diocese was formally established or created.
-
C.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
-
D.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
E.
establishedAsCurrentDiocese
Indicates that an ecclesiastical jurisdiction was formally constituted or recognized in its present status as a diocese.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 12:58 a.m.