Triple
T28514308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoa (northern part) |
E721572
|
entity |
| Predicate | administrativelyIncludedIn |
P63290
|
FINISHED |
| Object | modern Amhara Region |
—
|
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: modern Amhara Region | Statement: [Shoa (northern part), administrativelyIncludedIn, modern Amhara Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativelyIncludedIn Context triple: [Shoa (northern part), administrativelyIncludedIn, modern Amhara Region]
-
A.
administrativelyIn
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
B.
isAdministrativeUnitWithin
chosen
Indicates that one administrative unit is geographically or jurisdictionally contained within another administrative unit.
-
C.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
D.
containsAdministrativeTerritory
Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
-
E.
isAdministeredAsPartOf
Indicates that an action or treatment is given or carried out as a component within a larger procedure, regimen, or program.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 3:15 a.m.