Triple
T18926927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope John II |
E462997
|
entity |
| Predicate | adoptedNewNameDueTo |
P133821
|
FINISHED |
| Object | pagan connotations of his birth name Mercurius |
—
|
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: pagan connotations of his birth name Mercurius | Statement: [Pope John II, adoptedNewNameDueTo, pagan connotations of his birth name Mercurius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedNewNameDueTo Context triple: [Pope John II, adoptedNewNameDueTo, pagan connotations of his birth name Mercurius]
-
A.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
underwentNameChangeTo
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
D.
changedNameBy
Indicates that one entity altered or updated the name of another entity.
-
E.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bc36588190ae9cc3b8abf8afd4 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.