Triple
T25325093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold, Duke of Guelders |
E634989
|
entity |
| Predicate | soldSovereigntyTo |
P34009
|
FINISHED |
| Object | Charles the Bold |
—
|
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: Charles the Bold | Statement: [Arnold, Duke of Guelders, soldSovereigntyTo, Charles the Bold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldSovereigntyTo Context triple: [Arnold, Duke of Guelders, soldSovereigntyTo, Charles the Bold]
-
A.
countryReceivingSovereignty
Indicates the country that gains or is granted sovereign authority or control in a given context or agreement.
-
B.
lostSovereignty
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
-
C.
fullSovereigntyTransferred
chosen
Indicates that complete and exclusive governing authority has been formally transferred from one entity to another.
-
D.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
E.
sovereigntyClaimedFrom
Indicates that one entity asserts or has asserted sovereign authority or control that it derives from, or in place of, another entity.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f496928630819090e20713e47fb324 |
completed | May 1, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.