Triple
T27234090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Calculus Affair |
E682228
|
entity |
| Predicate | protagonistAlly |
P162271
|
FINISHED |
| Object | General Plekszy-Gladz’s opponents |
—
|
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: General Plekszy-Gladz’s opponents | Statement: [The Calculus Affair, protagonistAlly, General Plekszy-Gladz’s opponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistAlly Context triple: [The Calculus Affair, protagonistAlly, General Plekszy-Gladz’s opponents]
-
A.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
B.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
C.
primaryAlly
Indicates that one entity is the main or most significant ally or supportive partner of another entity.
-
D.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f626784b188190aaafe6e8123a12b9 |
completed | May 2, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:47 a.m.