Triple
T32838884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Democratic Republic |
E839908
|
entity |
| Predicate | claimsBasisIn |
P20568
|
FINISHED |
| Object | popular sovereignty |
—
|
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: popular sovereignty | Statement: [People's Democratic Republic, claimsBasisIn, popular sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsBasisIn Context triple: [People's Democratic Republic, claimsBasisIn, popular sovereignty]
-
A.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimedIn
Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
-
C.
claimsFoundationBy
chosen
Indicates that one entity asserts or declares that another entity serves as its basis, origin, or underlying foundation.
-
D.
claimsEffect
Indicates that one entity asserts or states that another entity has a particular effect or impact.
-
E.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:16 a.m.