Triple
T34684490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Imperial City of Weilburg |
E890705
|
entity |
| Predicate | followedConfession |
P198201
|
FINISHED |
| Object | Protestant |
—
|
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: Protestant | Statement: [Free Imperial City of Weilburg, followedConfession, Protestant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedConfession Context triple: [Free Imperial City of Weilburg, followedConfession, Protestant]
-
A.
followsConfession
Indicates that one event, action, or state occurs after and as a consequence of a confession.
-
B.
associatedConfession
Indicates a relationship where one entity is linked to a specific confession, admission, or statement acknowledging guilt or responsibility.
-
C.
linkedConfession
Indicates that one confession is connected or associated with another confession, typically as part of the same case, event, or narrative.
-
D.
confessionObtainedBy
Indicates that a confession was acquired through a particular method, action, or process.
-
E.
confessionUse
Indicates that one entity makes use of or relies on a confession in relation to another entity or context.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: May 1, 2026, 2:05 a.m.