Triple
T259469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Taiwan |
E5508
|
entity |
| Predicate | hasSynodOrConvention |
P2672
|
FINISHED |
| Object | diocesan convention |
—
|
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: diocesan convention | Statement: [Diocese of Taiwan, hasSynodOrConvention, diocesan convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSynodOrConvention Context triple: [Diocese of Taiwan, hasSynodOrConvention, diocesan convention]
-
A.
convenesBefore
Indicates that one event or gathering is convened and completed before another specified event or gathering begins.
-
B.
hasPlenaryChamber
Indicates that an institution or governing body possesses a designated plenary chamber where all members can meet and deliberate together.
-
C.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
D.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
E.
hasConference
chosen
Indicates that an entity organizes, hosts, or is associated with a specific conference.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.