Triple
T32004571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Warmia |
E817227
|
entity |
| Predicate | hadCanonInChapter |
P173492
|
FINISHED |
| Object | Nicolaus Copernicus |
—
|
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: Nicolaus Copernicus | Statement: [Bishop of Warmia, hadCanonInChapter, Nicolaus Copernicus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCanonInChapter Context triple: [Bishop of Warmia, hadCanonInChapter, Nicolaus Copernicus]
-
A.
hadChapterOf
Indicates that an entity (such as a book or document) includes or contains a specific chapter as one of its parts.
-
B.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
C.
hadChapterAt
Indicates that an organization or group maintained an official chapter, branch, or local unit at a specified location or institution.
-
D.
implementedInCanons
Indicates that something is realized, expressed, or carried out within a set of established rules, standards, or canonical works.
-
E.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:14 a.m.