Triple
T16828615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broederbond |
E409086
|
entity |
| Predicate | secrecyPractice |
P22701
|
FINISHED |
| Object | oaths of secrecy |
—
|
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: oaths of secrecy | Statement: [Broederbond, secrecyPractice, oaths of secrecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secrecyPractice Context triple: [Broederbond, secrecyPractice, oaths of secrecy]
-
A.
ritualSecrecy
Indicates that certain aspects of a ritual are intentionally concealed or restricted from outsiders or non-initiated participants.
-
B.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
-
C.
keepsSecretAbout
chosen
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
D.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
E.
secretive
Indicates that an entity deliberately withholds information or conceals its thoughts, actions, or intentions from others.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3151350819097b1c375e6df8986 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.