Triple
T24712510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miriam Makeba |
E612066
|
entity |
| Predicate | yearsOfExile |
P34025
|
FINISHED |
| Object | approximately 30 years |
—
|
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: approximately 30 years | Statement: [Miriam Makeba, yearsOfExile, approximately 30 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsOfExile Context triple: [Miriam Makeba, yearsOfExile, approximately 30 years]
-
A.
periodOfExile
chosen
Indicates a time span during which an entity is banished, expelled, or forced to live away from its native or rightful place.
-
B.
livedInExileIn
Indicates that an entity spent a period of time living outside its home country or usual place of residence due to exile, in a specified location.
-
C.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
D.
exiledWith
Indicates that two or more entities were banished or forced to leave a place together as part of the same exile.
-
E.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:25 a.m.