Triple
T22977603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alma Coin |
E571367
|
entity |
| Predicate | hiddenAgenda |
P91484
|
FINISHED |
| Object | establishing her own authoritarian regime |
—
|
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: establishing her own authoritarian regime | Statement: [Alma Coin, hiddenAgenda, establishing her own authoritarian regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenAgenda Context triple: [Alma Coin, hiddenAgenda, establishing her own authoritarian regime]
-
A.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
B.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
C.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
D.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
E.
secretlyOpposes
chosen
Indicates that one entity is acting against or resisting another entity or its goals without that opposition being openly known or acknowledged.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.