Triple
T32577093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Hanover |
E832674
|
entity |
| Predicate | linkedReligion |
P102165
|
FINISHED |
| Object | Protestantism |
—
|
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: Protestantism | Statement: [Prince of Hanover, linkedReligion, Protestantism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedReligion Context triple: [Prince of Hanover, linkedReligion, Protestantism]
-
A.
associatedReligionOrBelief
chosen
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
-
B.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
C.
orderReligion
Indicates that one entity prescribes, organizes, or regulates the religious practices, beliefs, or structure of another entity.
-
D.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
E.
sharesReligionWith
Indicates that two entities follow or are associated with the same religion or religious tradition.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:04 a.m.