Triple
T279403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natal Indian Congress |
E5319
|
entity |
| Predicate | campaignMethod |
P9029
|
FINISHED |
| Object | passive resistance |
—
|
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: passive resistance | Statement: [Natal Indian Congress, campaignMethod, passive resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignMethod Context triple: [Natal Indian Congress, campaignMethod, passive resistance]
-
A.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
B.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
C.
campaign
Indicates that an entity actively organizes or conducts a coordinated effort or series of actions aimed at achieving a specific goal, often in political, commercial, or social contexts.
-
D.
campaignManager
Indicates that one entity serves as the manager or coordinator responsible for planning, executing, and overseeing a campaign on behalf of another entity.
-
E.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
- F. None of above. chosen
Provenance (4 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25def95c48190bb8ab2259f67b583 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.