Triple
T33548003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah Baartman |
E859256
|
entity |
| Predicate | dateOfRepatriation |
P120523
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Sarah Baartman, dateOfRepatriation, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfRepatriation Context triple: [Sarah Baartman, dateOfRepatriation, 2002]
-
A.
repatriatedOn
chosen
Indicates that something or someone was returned to their country or place of origin on a specific date or time.
-
B.
repatriatedBy
Indicates that an entity is brought or returned back to its country or place of origin by a specified agent or authority.
-
C.
repatriationStatus
Indicates the current state or progress of returning a person or asset back to their country or original place of origin.
-
D.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
E.
dateOfSovereigntyTransfer
Indicates the date on which sovereignty or governing authority over an entity was formally transferred from one party to another.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:39 a.m.