Triple
T28244704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | combinedRole |
P108317
|
FINISHED |
| Object | secular ruler |
—
|
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: secular ruler | Statement: [Prince-Bishop of Lübeck, combinedRole, secular ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinedRole Context triple: [Prince-Bishop of Lübeck, combinedRole, secular ruler]
-
A.
combinesRoleOf
chosen
Indicates a relationship where a single entity simultaneously fulfills or merges multiple distinct roles or functions.
-
B.
complexRole
Indicates that an entity holds a multifaceted or composite role involving multiple responsibilities, functions, or relational aspects within a given context.
-
C.
unionRole
Indicates that an entity holds or is assigned a specific role within a labor union or similar collective organization.
-
D.
unificationRole
Indicates the role an entity plays in bringing together or reconciling multiple elements, groups, or concepts into a unified whole.
-
E.
associatedCollectiveRole
Indicates that an entity is linked to a role or function held within a collective, group, or organization.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11 p.m.