Triple
T25095238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadaksahak |
E628569
|
entity |
| Predicate | socialStatusHistorically |
P28623
|
FINISHED |
| Object | clients of Tuareg nobles |
—
|
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: clients of Tuareg nobles | Statement: [Tadaksahak, socialStatusHistorically, clients of Tuareg nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusHistorically Context triple: [Tadaksahak, socialStatusHistorically, clients of Tuareg nobles]
-
A.
historicalStatusOf
chosen
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
B.
socialHistoryFeature
Indicates a relationship where an entity is characterized by a specific aspect or feature of its social history (e.g., lifestyle, habits, or social circumstances).
-
C.
statusAfter1970
Indicates the status or condition of an entity as it exists after the year 1970.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b8893c81909fd77666ba04feec |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:24 a.m.