Triple
T8004716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African Constitution of 1983 |
E186335
|
entity |
| Predicate | entrenchedPolicy |
P58432
|
FINISHED |
| Object | racial segregation |
—
|
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: racial segregation | Statement: [South African Constitution of 1983, entrenchedPolicy, racial segregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrenchedPolicy Context triple: [South African Constitution of 1983, entrenchedPolicy, racial segregation]
-
A.
treatyOrPolicy
chosen
Indicates a formal agreement, treaty, or policy that establishes rules, obligations, or guidelines governing the relationship or behavior between entities.
-
B.
advancedPolicyOf
Indicates that one policy is a more developed, detailed, or progressive version of another policy.
-
C.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
D.
annexationPolicy
Indicates a policy or practice of formally incorporating one territory into the jurisdiction or sovereignty of another.
-
E.
ordinationPolicy
Indicates the rules or criteria governing how entities are ordered, ranked, or arranged relative to one 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf5fb588190ada4ec7d8087619c |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.