Triple
T23238116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Archdiocese of Kalocsa-Kecskemét |
E581358
|
entity |
| Predicate | mergedNameIncludes |
P9161
|
FINISHED |
| Object | Kalocsa |
—
|
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: Kalocsa | Statement: [Roman Catholic Archdiocese of Kalocsa-Kecskemét, mergedNameIncludes, Kalocsa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedNameIncludes Context triple: [Roman Catholic Archdiocese of Kalocsa-Kecskemét, mergedNameIncludes, Kalocsa]
-
A.
fullNameIncludes
chosen
Indicates that one entity’s full name contains another specified string or name component as a substring.
-
B.
renamedToInclude
Indicates that an entity has been renamed so that its new name explicitly includes another specified element (such as a term, identifier, or component).
-
C.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
D.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
E.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ea590c81908cd677d89f67d49f |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.