Triple
T891627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick I of Prussia |
E19250
|
entity |
| Predicate | elevated |
P3787
|
FINISHED |
| Object | Duchy of Prussia to Kingdom in Prussia |
—
|
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: Duchy of Prussia to Kingdom in Prussia | Statement: [Frederick I of Prussia, elevated, Duchy of Prussia to Kingdom in Prussia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevated Context triple: [Frederick I of Prussia, elevated, Duchy of Prussia to Kingdom in Prussia]
-
A.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
B.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
C.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
D.
crest
Indicates reaching the highest point or peak of something, such as a wave, hill, or trend, before it begins to decline.
-
E.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad019e448190ab991e85dc6d7708 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.