Triple
T9979134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilderberg Group |
E196404
|
entity |
| Predicate | participantProfile |
P91407
|
FINISHED |
| Object | political leaders |
—
|
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: political leaders | Statement: [Bilderberg Group, participantProfile, political leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantProfile Context triple: [Bilderberg Group, participantProfile, political leaders]
-
A.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
B.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
C.
userProfileFeatures
Indicates that certain characteristics, settings, or attributes are associated with and define a user's profile.
-
D.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
E.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb850bde48190a06b77757f8c081b |
completed | April 2, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:49 p.m.