Triple
T28904767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minipax |
E733041
|
entity |
| Predicate | goalsInFiction |
P118381
|
FINISHED |
| Object | maintain power of the Party |
—
|
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: maintain power of the Party | Statement: [Minipax, goalsInFiction, maintain power of the Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalsInFiction Context triple: [Minipax, goalsInFiction, maintain power of the Party]
-
A.
targetInFiction
Indicates that one entity is the target or subject of an action, focus, or effect within a fictional work or narrative context.
-
B.
hasFictionalGoal
chosen
Indicates that an entity is associated with a goal or objective that exists only within a fictional, imagined, or narrative context.
-
C.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
-
D.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
E.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ada0060819098ff14053a958b64 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:06 a.m.