Triple
T28796700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNLA |
E727103
|
entity |
| Predicate | regionCharacterizedAs |
P130244
|
FINISHED |
| Object | Sahara-Sahel |
—
|
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: Sahara-Sahel | Statement: [MNLA, regionCharacterizedAs, Sahara-Sahel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCharacterizedAs Context triple: [MNLA, regionCharacterizedAs, Sahara-Sahel]
-
A.
regionCharacter
Indicates a characteristic, feature, or quality that typifies or defines a particular region.
-
B.
regionalCharacteristic
chosen
Indicates that a particular feature, quality, or attribute is typical of, or distinctive to, a specific geographic region.
-
C.
regionallyRecognizedAs
Indicates that an entity is acknowledged or designated under a specific name, status, or classification within a particular geographic region or locality.
-
D.
regionRecognized
Indicates that a specific geographic or spatial region has been formally identified and acknowledged as valid or relevant within a given context.
-
E.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 28, 2026, 6:25 a.m.