Triple
T11400262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutten family |
E270088
|
entity |
| Predicate | hasMemberIdeology |
P31611
|
FINISHED |
| Object | support for the Protestant Reformation |
—
|
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: support for the Protestant Reformation | Statement: [Hutten family, hasMemberIdeology, support for the Protestant Reformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberIdeology Context triple: [Hutten family, hasMemberIdeology, support for the Protestant Reformation]
-
A.
hasIdeologicalPosition
chosen
Indicates that an entity holds, endorses, or is associated with a particular ideological stance or viewpoint.
-
B.
hasIdeologicalRole
Indicates that an entity holds or fulfills a specific function, position, or influence within an ideology or ideological framework.
-
C.
ideologyComponent
Indicates that one ideology is a constituent or defining part of another, broader ideology.
-
D.
hasMemberParty
Indicates that a group, organization, or coalition includes a specific party as one of its members.
-
E.
hasIdeologicalOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a particular ideology.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001adc188190ae45227856156412 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.