Triple
T5231535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGA |
E118120
|
entity |
| Predicate | typeOfAdvocacy |
P26857
|
FINISHED |
| Object | collective advocacy |
—
|
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: collective advocacy | Statement: [NGA, typeOfAdvocacy, collective advocacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAdvocacy Context triple: [NGA, typeOfAdvocacy, collective advocacy]
-
A.
advocacyOrganization
Indicates that an organization actively supports, promotes, or works on behalf of a cause, issue, or group through advocacy activities.
-
B.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
C.
areaOfActivism
Indicates the specific social, political, or environmental cause or issue that an entity actively advocates for or works to change.
-
D.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
E.
hasAdvocacyMethod
chosen
Indicates the method, strategy, or approach used to advocate for a cause, issue, or 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0223148190be88d737c25d60d7 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.