Triple
T21378847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert, Duke of Prussia |
E527286
|
entity |
| Predicate | officeStartAsGrandMaster |
P73129
|
FINISHED |
| Object | 1511 |
—
|
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: 1511 | Statement: [Albert, Duke of Prussia, officeStartAsGrandMaster, 1511]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartAsGrandMaster Context triple: [Albert, Duke of Prussia, officeStartAsGrandMaster, 1511]
-
A.
grandMaster
Indicates that one entity holds the highest authoritative or mastery status over a domain, discipline, or organization in relation to another entity.
-
B.
officeStartAsPontifexMaximus
Indicates the point in time when an individual begins their tenure in the office of Pontifex Maximus.
-
C.
officeStartAsTriumvir
Indicates that an entity begins holding an office or position specifically in the role of a triumvir (one of three joint officeholders).
-
D.
managementRoleStart
chosen
Indicates the date or point in time when an entity begins holding a particular management role or position.
-
E.
monarchAsGrandMaster
Indicates that a monarch holds the position and authority of a grand master within an order 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0cb138081909bcbf295483656cb |
completed | April 22, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:11 p.m.