Triple
T1973975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastian Rudolph |
E42864
|
entity |
| Predicate | hasNotableRoleType |
P22252
|
FINISHED |
| Object | historical roles |
—
|
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: historical roles | Statement: [Sebastian Rudolph, hasNotableRoleType, historical roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRoleType Context triple: [Sebastian Rudolph, hasNotableRoleType, historical roles]
-
A.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
hasNotablePosition
chosen
Indicates that an entity holds or has held a position, role, or office considered notable or significant.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
D.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
-
E.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f6c4208190a41e02733faed8df |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.