Triple
T16828625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broederbond |
E409086
|
entity |
| Predicate | archivesOpened |
P125005
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Broederbond, archivesOpened, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesOpened Context triple: [Broederbond, archivesOpened, 1990s]
-
A.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
B.
archivesHeldBy
Indicates that archival materials or records are kept, managed, or preserved by a particular entity.
-
C.
archiveAvailability
Indicates whether something is stored or accessible in an archive, and under what conditions it can be retrieved.
-
D.
archiveContent
Indicates that content is being stored or moved into an archive state for long-term retention or historical reference.
-
E.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
- F. None of above. chosen
Provenance (4 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b315dbbc81908a1c83069e058770 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.