Triple
T3558767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appendix II |
E75282
|
entity |
| Predicate | requiresDocumentation |
P100
|
FINISHED |
| Object | CITES permits and certificates accompanying shipments |
—
|
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: CITES permits and certificates accompanying shipments | Statement: [Appendix II, requiresDocumentation, CITES permits and certificates accompanying shipments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDocumentation Context triple: [Appendix II, requiresDocumentation, CITES permits and certificates accompanying shipments]
-
A.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
B.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
C.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
D.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
E.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0881d50819092332491b9527c9d |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.