Triple
T5240523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anant Singh |
E118327
|
entity |
| Predicate | notableThemeInWork |
P7671
|
FINISHED |
| Object | apartheid |
—
|
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: apartheid | Statement: [Anant Singh, notableThemeInWork, apartheid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableThemeInWork Context triple: [Anant Singh, notableThemeInWork, apartheid]
-
A.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
B.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
C.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
D.
settingOfNotableWork
Indicates that a particular place or environment serves as the primary setting where a notable work (such as a book, film, or play) takes place.
-
E.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b2a52fc8190a22631e1853c74a3 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.