Triple
T29302556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fadicca-Mahas |
E742998
|
entity |
| Predicate | inhabitsHistorically |
P130010
|
FINISHED |
| Object | northern Sudan |
—
|
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: northern Sudan | Statement: [Fadicca-Mahas, inhabitsHistorically, northern Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitsHistorically Context triple: [Fadicca-Mahas, inhabitsHistorically, northern Sudan]
-
A.
historicalHabitat
chosen
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
B.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
C.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
-
D.
historicallyObservedIn
Indicates that something has been recorded or documented as occurring, existing, or taking place within a particular historical context, period, or location.
-
E.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a3b30081908c86ede33ebeb099 |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:10 p.m.