Triple
T30959873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bole ethnic group |
E788780
|
entity |
| Predicate | possiblePresence |
P155838
|
FINISHED |
| Object | border areas of Niger |
—
|
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: border areas of Niger | Statement: [Bole ethnic group, possiblePresence, border areas of Niger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblePresence Context triple: [Bole ethnic group, possiblePresence, border areas of Niger]
-
A.
possiblePresenceIn
chosen
Indicates that an entity may be located in, occur in, or exist within a specified place, context, or container, without asserting that it is definitively present there.
-
B.
statePresence
Indicates that an entity exists, operates, or is present within a particular state or governmental jurisdiction.
-
C.
onlinePresence
Indicates that an entity maintains a presence or representation on the internet, such as through websites, profiles, or digital platforms.
-
D.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
-
E.
requestedPresenceOf
Indicates that one entity has asked or required another entity to be present at a specific place, time, or event.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 8:54 p.m.