Triple
T17421122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumark region |
E423616
|
entity |
| Predicate | cameUnderBrandenburgRule |
P47649
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Neumark region, cameUnderBrandenburgRule, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameUnderBrandenburgRule Context triple: [Neumark region, cameUnderBrandenburgRule, 13th century]
-
A.
endOfRuleOverPrussia
Indicates the point in time or event at which governing authority or rule over Prussia comes to an end.
-
B.
successorAsKingOfPrussia
Indicates that one person became the next king of Prussia following another person.
-
C.
successorAsDukeOfSilesia
Indicates that one entity became the next holder of the title Duke of Silesia after another entity, succeeding them in that ducal position.
-
D.
laterUnderRuleOf
chosen
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
E.
endedAsPrincipality
Indicates that an entity’s existence or historical development concluded with it having the political status of a principality.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e442372954819085f332efc7067ae9 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.