Triple
T7381419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Lippe |
E170260
|
entity |
| Predicate | lostSovereignty |
P76678
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Prince of Lippe, lostSovereignty, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostSovereignty Context triple: [Prince of Lippe, lostSovereignty, 1918]
-
A.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
B.
reducedSovereigntyOf
Indicates that one entity has diminished, constrained, or otherwise limited the sovereignty or autonomous decision-making power of another entity.
-
C.
lostAdministrativePrimacyTo
Indicates that one entity ceased to be the primary administrative authority and that this leading administrative role was transferred to another entity.
-
D.
lostContinentalTerritory
Indicates that one entity has lost control over part or all of its mainland territorial holdings to another entity or as a result of some event.
-
E.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
- F. None of above. chosen
Provenance (4 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1c7b5bc81908afa2bf39159979b |
completed | March 27, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0ebf9c88190af5a4d87d3fd338a |
completed | March 27, 2026, 9:04 p.m. |
Created at: March 27, 2026, 3:08 p.m.