Triple
T3909432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijaw people |
E87284
|
entity |
| Predicate | notableStruggle |
P36801
|
FINISHED |
| Object | resource control agitation |
—
|
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: resource control agitation | Statement: [Ijaw people, notableStruggle, resource control agitation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStruggle Context triple: [Ijaw people, notableStruggle, resource control agitation]
-
A.
notableStruggles
chosen
Indicates that the subject has faced significant challenges, difficulties, or adversities that are especially noteworthy or defining.
-
B.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
C.
meansOfStruggle
Indicates the method, tactic, or form of action used by an entity in carrying out a struggle or conflict.
-
D.
associatedWithStruggle
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
-
E.
notableConflictWith
Indicates a significant, recognized conflict or dispute that exists or has existed between the related entities.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.