Triple
T30783172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wormditt |
E783877
|
entity |
| Predicate | sovereigntyChangedFrom |
P158354
|
FINISHED |
| Object | Germany |
—
|
NE NERFINISHED |
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: Germany | Statement: [Wormditt, sovereigntyChangedFrom, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereigntyChangedFrom Context triple: [Wormditt, sovereigntyChangedFrom, Germany]
-
A.
fullSovereigntyTransferred
Indicates that complete and exclusive governing authority has been formally transferred from one entity to another.
-
B.
sovereigntyClaimedFrom
Indicates that one entity asserts or has asserted sovereign authority or control that it derives from, or in place of, another entity.
-
C.
sovereignStateBefore
chosen
Indicates that one entity functioned as the sovereign state governing another entity during an earlier historical period.
-
D.
sovereigntyFormedBy
Indicates that a sovereignty or governing authority comes into existence through the actions, decisions, or processes of a specified agent or mechanism.
-
E.
sovereigntyHolder
Indicates which entity possesses ultimate governing authority or sovereign control over another entity or territory.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:41 p.m.