Triple
T28430193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Christburg |
E715101
|
entity |
| Predicate | partyRepresentingTeutonicOrder |
P173248
|
FINISHED |
| Object | Grand Master of the Teutonic Order |
—
|
NE NERFINISHED |
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: Grand Master of the Teutonic Order | Statement: [Treaty of Christburg, partyRepresentingTeutonicOrder, Grand Master of the Teutonic Order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyRepresentingTeutonicOrder Context triple: [Treaty of Christburg, partyRepresentingTeutonicOrder, Grand Master of the Teutonic Order]
-
A.
intendedStatusOfGrandDuchyOfRuthenia
Indicates the planned or desired political or legal status assigned to the Grand Duchy of Ruthenia.
-
B.
SaxonElector
Indicates that an entity holds (or held) the position of Elector of Saxony within the Holy Roman Empire.
-
C.
successorInVolhynia
Indicates that one entity directly followed another in holding authority or position in Volhynia.
-
D.
GermanyConfederation
Indicates that an entity is or was a member of the German Confederation.
-
E.
firstReichProtector
Indicates that the subject served as the first protector (or guardian authority) of the specified Reich.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 28, 2026, 1:39 a.m.