Triple
T20370737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnes |
E497043
|
entity |
| Predicate | actsAgainst |
P70478
|
FINISHED |
| Object | controlling 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: controlling regime | Statement: [Barnes, actsAgainst, controlling regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actsAgainst Context triple: [Barnes, actsAgainst, controlling regime]
-
A.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
B.
oppositionActivity
chosen
Indicates that one entity engages in actions or behaviors that resist, counter, or work against another entity, its goals, or its activities.
-
C.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
D.
operatesAgainst
Indicates that one entity takes action to oppose, counter, or target another entity as an adversary or obstacle.
-
E.
disciplinaryActionsAgainstSupporters
Indicates that some authority imposes disciplinary measures on individuals who are supporters of a particular person, group, or cause.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678758b98819082c6440e03ad1615 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.