Triple
T16280164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Šokci |
E395242
|
entity |
| Predicate | ethnoreligiousCharacter |
P8262
|
FINISHED |
| Object | Catholic |
—
|
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: Catholic | Statement: [Šokci, ethnoreligiousCharacter, Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoreligiousCharacter Context triple: [Šokci, ethnoreligiousCharacter, Catholic]
-
A.
ethnoreligiousIdentity
chosen
Indicates a relationship where an entity is characterized by a combined ethnic and religious group identity.
-
B.
hasEthnoReligiousDimension
Indicates that the relationship, event, or phenomenon involves or is characterized by an ethnic and/or religious aspect or component.
-
C.
ethnicOrReligiousGroup
Indicates that one entity is an ethnic or religious group to which the other entity belongs or with which it is associated.
-
D.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
E.
religiousCharacteristic
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24611926c81909b276ca3f406f15d |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.