Triple
T5178037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Prussia |
E116847
|
entity |
| Predicate | titleElevationResultedIn |
P25426
|
FINISHED |
| Object | coronation of Frederick I as King in Prussia in 1701 |
—
|
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: coronation of Frederick I as King in Prussia in 1701 | Statement: [Duke of Prussia, titleElevationResultedIn, coronation of Frederick I as King in Prussia in 1701]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleElevationResultedIn Context triple: [Duke of Prussia, titleElevationResultedIn, coronation of Frederick I as King in Prussia in 1701]
-
A.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
titleSucceededFrom
Indicates that a person or entity obtained a title previously held by another, directly following them in succession.
-
C.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
-
D.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
-
E.
titleBecomes
chosen
Indicates that one title changes into or is replaced by another title over time.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7976339481909ece900de22064f2 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.