Triple
T12805637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Esztergom-Budapest |
E306136
|
entity |
| Predicate | mergedNameAdopted |
P39961
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Archdiocese of Esztergom-Budapest, mergedNameAdopted, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedNameAdopted Context triple: [Archdiocese of Esztergom-Budapest, mergedNameAdopted, 1993]
-
A.
currentNameAdoptedBy
Indicates that an entity has adopted or started using a particular current name.
-
B.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
C.
adoptiveNomen
Indicates a naming relationship where one entity has taken on or been given the name of another in an adoptive or non-biological sense.
-
D.
laterAdoptedBy
Indicates that one entity is adopted by another entity at a later point in time, after some prior state or relationship has already been established.
-
E.
changedNameIn
chosen
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.