Triple
T7000837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Poland |
E162331
|
entity |
| Predicate | hasHighAdherenceRate |
P73506
|
FINISHED |
| Object | Polish population |
—
|
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: Polish population | Statement: [Catholic Church in Poland, hasHighAdherenceRate, Polish population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighAdherenceRate Context triple: [Catholic Church in Poland, hasHighAdherenceRate, Polish population]
-
A.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
hasHighRatingOn
Indicates that one entity is evaluated or reviewed on another entity’s platform or system with a rating that meets or exceeds a defined high threshold.
-
C.
hasHighPointStatus
Indicates that an entity holds a high or elevated status within a point-based or ranking system.
-
D.
hasHighPropertyValues
Indicates that the associated entity possesses property values that are above a defined or typical threshold.
-
E.
successRate
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
- F. None of above. chosen
Provenance (4 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.