Triple
T25588288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hjalmar Gullberg |
E641446
|
entity |
| Predicate | religious influence |
P29112
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Hjalmar Gullberg, religious influence, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religious influence Context triple: [Hjalmar Gullberg, religious influence, Christianity]
-
A.
influencedReligion
Indicates that one entity has had a shaping or modifying effect on the religious beliefs, practices, or traditions of another entity.
-
B.
influencedByReligion
chosen
Indicates that an entity’s characteristics, decisions, or development are shaped or affected by religious beliefs, practices, or institutions.
-
C.
laterInfluencedByReligion
Indicates that an entity was influenced at a later time by a particular religion or religious tradition.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 21, 2026, 4:18 p.m.