Triple
T7845722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act No. 30 of 1950 |
E181917
|
entity |
| Predicate | ideologySupported |
P31611
|
FINISHED |
| Object | white minority rule |
—
|
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: white minority rule | Statement: [Act No. 30 of 1950, ideologySupported, white minority rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ideologySupported Context triple: [Act No. 30 of 1950, ideologySupported, white minority rule]
-
A.
ideologyComponent
Indicates that one ideology is a constituent or defining part of another, broader ideology.
-
B.
ideology
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
C.
hasIdeologicalPosition
chosen
Indicates that an entity holds, endorses, or is associated with a particular ideological stance or viewpoint.
-
D.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
E.
ideologicalCore
Indicates that one entity represents the central or foundational set of beliefs, values, or principles that fundamentally shape and guide another entity’s ideology.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163f5da08190b7340ef4cc01cd19 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.