Triple
T18911764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Somaliland |
E462625
|
entity |
| Predicate | statusOfCountry |
P18803
|
FINISHED |
| Object | self-declared state |
—
|
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: self-declared state | Statement: [Parliament of Somaliland, statusOfCountry, self-declared state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfCountry Context triple: [Parliament of Somaliland, statusOfCountry, self-declared state]
-
A.
countrySpecificStatus
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
B.
countryStatus
chosen
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
-
C.
GIStatusCountry
Indicates the status or condition of a geographic indication (GI) within a specific country.
-
D.
countryWithOfficialStatus
Indicates that a country holds an official, legally recognized status in relation to the referenced entity.
-
E.
continentStatus
Indicates the status or condition assigned to a continent, such as its current state, classification, or role within a given context.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c6238e288190b30311b5d80beafb |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.