Triple
T24886049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tebunginako |
E622853
|
entity |
| Predicate | hasIssueDocumentedBy |
P143647
|
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: [Tebunginako, hasIssueDocumentedBy, environmental NGOs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssueDocumentedBy Context triple: [Tebunginako, hasIssueDocumentedBy, environmental NGOs]
-
A.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
B.
hasCertificationIssueIn
Indicates that an entity has a certification-related problem, defect, or noncompliance occurring within a specified context, scope, or location.
-
C.
hasIssueRecognizedBy
chosen
Indicates that an issue or problem is acknowledged, identified, or formally recognized by a particular entity.
-
D.
hasRecentIssue
Indicates that an entity is associated with an issue or problem that has occurred within a recent or specified time frame.
-
E.
hadIssue
Indicates that an entity experienced, encountered, or was affected by a particular problem, defect, or difficulty.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:25 a.m.