Triple
T30462290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzacium |
E775044
|
entity |
| Predicate | hasEcclesiasticalImportance |
P169776
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Byzacium, hasEcclesiasticalImportance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcclesiasticalImportance Context triple: [Byzacium, hasEcclesiasticalImportance, yes]
-
A.
hasLiturgicalImportance
Indicates that something holds recognized significance or special status within religious worship or liturgical practice.
-
B.
hasEcclesiasticalInfluenceIn
Indicates that an entity holds religious or church-related authority, impact, or sway within a specified region, institution, or context.
-
C.
hasReligiousSignificanceVia
Indicates that something holds religious significance specifically by means of, or through the mediation of, another entity, event, or context.
-
D.
hasEcclesiasticalHistoryPeriod
Indicates that something is associated with, belongs to, or falls within a particular period in ecclesiastical (church) history.
-
E.
celebratedInChurch
Indicates that a ceremony, event, or occasion is formally observed or performed within a church setting.
- F. None of above. chosen
Provenance (4 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f0d838819099ca4d828a246d7f |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:10 p.m.