Triple
T1179360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Polish Republic |
E25099
|
entity |
| Predicate | hasSovereignty |
P5545
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Third Polish Republic, hasSovereignty, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovereignty Context triple: [Third Polish Republic, hasSovereignty, yes]
-
A.
sovereigntyStatus
chosen
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
B.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
C.
sovereigntyBasedOn
Indicates that one entity’s sovereignty or governing authority is derived from, justified by, or contingent upon another specified basis or source.
-
D.
sovereignClaimedBy
Indicates that a territory or entity is asserted to be under the sovereignty or ultimate authority of a particular claimant.
-
E.
sovereigntyLocation
Indicates the place or territory over which an entity holds sovereign authority or jurisdiction.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.