Triple
T17981734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikarna |
E449616
|
entity |
| Predicate | roleInDiceGame |
P129998
|
FINISHED |
| Object | voice of dissent |
—
|
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: voice of dissent | Statement: [Vikarna, roleInDiceGame, voice of dissent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDiceGame Context triple: [Vikarna, roleInDiceGame, voice of dissent]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
roleInDomino
Indicates that an entity participates in a domino effect or chain of events by occupying a specific role or position within that causal sequence.
-
C.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
D.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
E.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b20431588190a5fe2148a61de403 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.