Triple
T2489038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Border Protection Troops |
E51995
|
entity |
| Predicate | opposedActivity |
P437
|
FINISHED |
| Object | smuggling |
—
|
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: smuggling | Statement: [Border Protection Troops, opposedActivity, smuggling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedActivity Context triple: [Border Protection Troops, opposedActivity, smuggling]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedQualityTo
Indicates that one quality stands in direct opposition or contrast to another quality.
-
C.
opposedConference
Indicates that one entity actively resists, counters, or works against another entity within the context of a conference or formal gathering.
-
D.
oppositionMovement
Indicates a relationship where a group or entity actively resists, challenges, or seeks to change an existing authority, policy, regime, or dominant force.
-
E.
opposedConversionOf
Indicates that one entity actively resisted, objected to, or worked against the process of converting or changing another entity.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.