Triple
T21378848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert, Duke of Prussia |
E527286
|
entity |
| Predicate | officeEndAsGrandMaster |
P2941
|
FINISHED |
| Object | 1525 |
—
|
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: 1525 | Statement: [Albert, Duke of Prussia, officeEndAsGrandMaster, 1525]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeEndAsGrandMaster Context triple: [Albert, Duke of Prussia, officeEndAsGrandMaster, 1525]
-
A.
officeEndAsPremier
Indicates the point in time or event at which an individual's term serving as premier comes to an end.
-
B.
grandMaster
Indicates that one entity holds the highest authoritative or mastery status over a domain, discipline, or organization in relation to another entity.
-
C.
formerGrandMaster
Indicates that a person once held the title of Grand Master but no longer holds that position.
-
D.
officeEnded
chosen
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
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.