Triple
T29452519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast "Bandit Suppression" Headquarters |
E747010
|
entity |
| Predicate | labelsOpponentsAs |
P48619
|
FINISHED |
| Object | bandits |
—
|
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: bandits | Statement: [Northeast "Bandit Suppression" Headquarters, labelsOpponentsAs, bandits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelsOpponentsAs Context triple: [Northeast "Bandit Suppression" Headquarters, labelsOpponentsAs, bandits]
-
A.
consideredOpponentsAs
chosen
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
B.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
C.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
-
D.
allegedByOpponents
Indicates that a claim or accusation is made by opponents of the subject.
-
E.
opponentSupporters
Indicates that the related entities are supporters or backers of opposing sides in a contest, conflict, or competition.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 3:33 p.m.