Triple
T3452824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutonic Order |
E72830
|
entity |
| Predicate | dissolutionAsSovereignState |
P43452
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Teutonic Order, dissolutionAsSovereignState, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolutionAsSovereignState Context triple: [Teutonic Order, dissolutionAsSovereignState, 16th century]
-
A.
sovereignStateAfter
Indicates that one sovereign state succeeds another as its political or legal successor in time.
-
B.
wasIndependentUntil
chosen
Indicates that an entity possessed independent status or autonomy up to a specific point in time, after which that independence ceased.
-
C.
countryAfterDissolution
Indicates that one country emerged or existed as a successor state following the dissolution of another country.
-
D.
numberOfUnionRepublicsAtDissolution
Indicates the total count of union republics that existed in a state at the time of its dissolution.
-
E.
establishedAsCommonwealthBy
Indicates that an entity was formally constituted or recognized as a commonwealth by another specified authority or agent.
- 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_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. |
Created at: March 8, 2026, 3:16 p.m.