Triple
T16946574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raków |
E411082
|
entity |
| Predicate | religiousProfile |
P45
|
FINISHED |
| Object | center of the Polish Brethren |
—
|
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: center of the Polish Brethren | Statement: [Raków, religiousProfile, center of the Polish Brethren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousProfile Context triple: [Raków, religiousProfile, center of the Polish Brethren]
-
A.
religiousCharacteristic
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
-
B.
religiousOrientationRole
Indicates a role or position that an entity holds in relation to a particular religious orientation or affiliation.
-
C.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
D.
religiousName
Indicates that an entity has or is known by a name specifically associated with a religious role, identity, or context.
-
E.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb25e0c8190948e62d9575ae9cd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.