Triple
T31592877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shewa |
E806147
|
entity |
| Predicate | wasProvince |
P172589
|
FINISHED |
| Object | Shewa Province |
—
|
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: Shewa Province | Statement: [Shewa, wasProvince, Shewa Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasProvince Context triple: [Shewa, wasProvince, Shewa Province]
-
A.
hadProvince
Indicates that a governing entity possessed administrative control or jurisdiction over a specific province.
-
B.
wasStateCapitalOf
Indicates that a city previously served as the official capital of a specified state or equivalent political region.
-
C.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
D.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
E.
laterProvinceName
Indicates that an entity (such as a region or administrative unit) is known by a different province name at a later point in time.
- F. None of above. chosen
Provenance (4 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 10:29 p.m.