Triple
T7318255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penan |
E168468
|
entity |
| Predicate | advocacySupportFrom |
P33
|
FINISHED |
| Object | environmental NGOs |
—
|
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: environmental NGOs | Statement: [Penan, advocacySupportFrom, environmental NGOs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocacySupportFrom Context triple: [Penan, advocacySupportFrom, environmental NGOs]
-
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.
hasAdvocacyMethod
Indicates the method, strategy, or approach used to advocate for a cause, issue, or entity.
-
D.
advocates
chosen
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
E.
politicalSupporter
Indicates that one entity supports, endorses, or aligns with the political views, actions, or position of 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef18b7bc81908a9ee405d684f304 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.