Triple
T3452812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutonic Order |
E72830
|
entity |
| Predicate | suppressedInPrussia |
P48301
|
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: [Teutonic Order, suppressedInPrussia, 1525]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppressedInPrussia Context triple: [Teutonic Order, suppressedInPrussia, 1525]
-
A.
suppressedAsPrinceBishopric
Indicates that a prince-bishopric (an ecclesiastical territory ruled by a bishop with princely authority) was formally abolished or dissolved as a political-ecclesiastical entity.
-
B.
timeInKingdomOfPrussia
Indicates that an entity spent a specified period of time within the Kingdom of Prussia.
-
C.
capturedStandardsByPrussia
Indicates that military standards or flags were seized or taken as trophies by Prussia from another party.
-
D.
endOfRuleOverPrussia
Indicates the point in time or event at which governing authority or rule over Prussia comes to an end.
-
E.
suppressedDuring
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa2f5ec81909ced93c01e8fe38b |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.