Triple
T28661537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Illyricum |
E725479
|
entity |
| Predicate | correspondsInPartToModern |
P84931
|
FINISHED |
| Object | Croatia |
—
|
NE NERFINISHED |
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: Croatia | Statement: [Diocese of Illyricum, correspondsInPartToModern, Croatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsInPartToModern Context triple: [Diocese of Illyricum, correspondsInPartToModern, Croatia]
-
A.
partlyCorrespondsToModernDepartment
chosen
Indicates that an entity’s historical or former administrative area overlaps only in part with the boundaries of a specified modern department.
-
B.
isModernFormOf
Indicates that one entity is a newer or contemporary version, adaptation, or evolution of another earlier entity.
-
C.
modernEquivalent
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
-
D.
partOfPresentDay
Indicates that one entity is a component, region, or subset of what constitutes the other entity in its current, modern-day form.
-
E.
accuracyComparedToModern
Indicates how the accuracy of something compares relative to that of a modern counterpart or standard.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 4:58 a.m.