Triple
T9944082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Delegates of South Africa |
E194158
|
entity |
| Predicate | racialSegregationBasis |
P15323
|
FINISHED |
| Object | Indian |
—
|
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: Indian | Statement: [House of Delegates of South Africa, racialSegregationBasis, Indian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialSegregationBasis Context triple: [House of Delegates of South Africa, racialSegregationBasis, Indian]
-
A.
segregationBasis
chosen
Indicates the criterion or characteristic used as the basis for separating or distinguishing one group or set from another.
-
B.
stanceOnSegregation
Indicates a person or group’s expressed position, attitude, or viewpoint regarding racial or social segregation.
-
C.
typeOfSegregationAddressed
Indicates the specific form or category of segregation that is being targeted, handled, or dealt with in a given context.
-
D.
segregationEra
Indicates a period or context in which entities are subject to racially discriminatory separation or unequal treatment under segregation policies.
-
E.
raceRole
Indicates the specific role, position, or function an entity holds within a race or racing 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb613fbb48190b82a06987310cc96 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.