Triple
T35364897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penkun |
E1021601
|
entity |
| Predicate | dominantDenominationHistorically |
P5897
|
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: [Penkun, dominantDenominationHistorically, Protestantism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantDenominationHistorically Context triple: [Penkun, dominantDenominationHistorically, Protestantism]
-
A.
historicalDenomination
Indicates that an entity was formerly associated with or belonged to a particular denomination or sect at some point in the past.
-
B.
earliestMainDenomination
Indicates the earliest primary denomination or category to which an entity is associated in time.
-
C.
eraOfBillsDominance
Indicates a time period during which the Bills consistently dominated their competition or league.
-
D.
historicallyDominantIn
chosen
Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
-
E.
denominationFounded
Indicates that one entity established or created a particular religious denomination.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:03 p.m.