Triple
T32626851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steering Committee (Bilderberg) |
E834080
|
entity |
| Predicate | publicTransparency |
P34462
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Steering Committee (Bilderberg), publicTransparency, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicTransparency Context triple: [Steering Committee (Bilderberg), publicTransparency, low]
-
A.
transparency
chosen
Indicates that an entity’s internal processes, information, or decision-making are openly accessible and understandable to others.
-
B.
publicAccess
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
C.
transparencyRole
Indicates that one entity serves a function or position related to ensuring or embodying transparency in relation to another entity.
-
D.
isTransparent
Indicates that one entity allows light or information to pass through it such that other entities behind or within it can be clearly perceived.
-
E.
coversDisclosureOf
Indicates that one entity’s scope, terms, or provisions include and apply to the act or content of another entity’s disclosure.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:06 a.m.