Triple
T4675756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nonviolence movement |
E103675
|
entity |
| Predicate | tacticsInclude |
P1716
|
FINISHED |
| Object | boycott |
—
|
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: boycott | Statement: [nonviolence movement, tacticsInclude, boycott]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsInclude Context triple: [nonviolence movement, tacticsInclude, boycott]
-
A.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
C.
hasCommonTacticOfOpponents
Indicates that two or more entities share the same tactic or strategy used by their respective opponents.
-
D.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
E.
defensiveTactics
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.