Triple
T33118256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dame Vaako |
E847516
|
entity |
| Predicate | strategies |
P31887
|
FINISHED |
| Object | political intrigue |
—
|
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 intrigue | Statement: [Dame Vaako, strategies, political intrigue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategies Context triple: [Dame Vaako, strategies, political intrigue]
-
A.
strategizesFor
Indicates that one entity plans or devises strategies on behalf of, or in support of, another entity.
-
B.
strategyType
chosen
Indicates the specific kind or category of strategy associated with an entity or action.
-
C.
strategicLogic
Indicates a relationship where an entity applies structured, goal-oriented reasoning or decision rules to plan, choose, or justify actions in pursuit of strategic objectives.
-
D.
الاستراتيجية
Indicates a strategic relationship in which an entity plans, organizes, or directs actions and resources to achieve specific long-term goals or advantages.
-
E.
strategicAspect
Indicates that something pertains to a strategic dimension, such as long-term planning, positioning, or high-level decision-making within a broader context.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:27 a.m.