Triple
T38382284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burzum |
E893786
|
entity |
| Predicate | primaryMember |
P17104
|
FINISHED |
| Object | Varg Vikernes |
E1564834
|
NE 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: Varg Vikernes | Statement: [Burzum, primaryMember, Varg Vikernes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMember Context triple: [Burzum, primaryMember, Varg Vikernes]
-
A.
primaryMembers
chosen
Indicates that the related entities are the main or most important members within a larger group or organization.
-
B.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
C.
primaryAccountIn
Indicates that an entity serves as the main or default account within a specified context, group, or container.
-
D.
primaryPatron
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- F. None of above.
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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cc9b279481908e6c3f1feb43a529 |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.