Triple
T33790524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POPRC |
E865918
|
entity |
| Predicate | usesCriteriaFrom |
P6249
|
FINISHED |
| Object | Annex D of the Stockholm Convention |
—
|
NE NERFINISHED |
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: Annex D of the Stockholm Convention | Statement: [POPRC, usesCriteriaFrom, Annex D of the Stockholm Convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCriteriaFrom Context triple: [POPRC, usesCriteriaFrom, Annex D of the Stockholm Convention]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
establishesCriterion
Indicates that an entity defines or sets a standard, rule, or condition by which another entity is to be judged, selected, or evaluated.
-
C.
proposesCriterion
Indicates that one entity suggests or puts forward a specific criterion to be considered or used by another entity or within a given context.
-
D.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
valueCriterion
Indicates that something is evaluated or selected based on a specified standard, rule, or measure of value.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 1:45 a.m.