Triple

T27999101
Position Surface form Disambiguated ID Type / Status
Subject Slovak Rome E707097 entity
Predicate associatedWith P37 FINISHED
Object Trnava Archdiocese
The Trnava Archdiocese is a prominent Roman Catholic ecclesiastical territory in western Slovakia, often nicknamed the "Slovak Rome" for its historical and religious significance.
E1796297 NE 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: Trnava Archdiocese | Statement: [Slovak Rome, associatedWith, Trnava Archdiocese]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Trnava Archdiocese
Triple: [Slovak Rome, associatedWith, Trnava Archdiocese]
Generated description
The Trnava Archdiocese is a prominent Roman Catholic ecclesiastical territory in western Slovakia, often nicknamed the "Slovak Rome" for its historical and religious significance.

Provenance (5 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_69ef96b980d88190a753b2f9a978595a completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63badb94c8190a6a18d86b505629e completed May 2, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_6a13118830a48190800e40fe201b5652 completed May 24, 2026, 2:56 p.m.
NEDg Description generation batch_6a1312d77e84819090f3a3518ec97726 completed May 24, 2026, 3:01 p.m.
NED2 Entity disambiguation (via description) batch_6a13143573d881908f94a0403cf70ceb completed May 24, 2026, 3:07 p.m.
Created at: April 27, 2026, 7:55 p.m.