Triple
T2268873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohenzollern-Sigmaringen |
E50610
|
entity |
| Predicate | elevationToPrincipality |
P34314
|
FINISHED |
| Object | 1623 |
—
|
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: 1623 | Statement: [Hohenzollern-Sigmaringen, elevationToPrincipality, 1623]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToPrincipality Context triple: [Hohenzollern-Sigmaringen, elevationToPrincipality, 1623]
-
A.
elevationToPrincipalityDate
chosen
Indicates the date on which an entity was formally elevated to the status of a principality.
-
B.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc39c6ff0819081a07696f1c29990 |
completed | March 7, 2026, 6:20 a.m. |
| PD | Predicate disambiguation | batch_69abbdb7719081909143efa8f48df4e4 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.