Triple
T33192133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annexe I (CITES) |
E849637
|
entity |
| Predicate | hasStricterRegimeThan |
P50345
|
FINISHED |
| Object | Annexe II (CITES) |
—
|
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: Annexe II (CITES) | Statement: [Annexe I (CITES), hasStricterRegimeThan, Annexe II (CITES)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStricterRegimeThan Context triple: [Annexe I (CITES), hasStricterRegimeThan, Annexe II (CITES)]
-
A.
hasStricterTradeControlsThan
chosen
Indicates that one entity enforces more restrictive or rigorous trade regulations or controls than another entity.
-
B.
requiresStricterRegulationsThan
Indicates that one entity must be governed by more stringent or demanding regulations than another entity.
-
C.
hasLessStrictTradeControlsThan
Indicates that one entity’s trade regulations or restrictions are more relaxed or permissive compared to those of another entity.
-
D.
hasSpecialRegimeFor
Indicates that one entity applies a distinct or exceptional set of rules, conditions, or treatments specifically tailored for another entity.
-
E.
hasStricterStandardThan
Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:29 a.m.