Triple
T15387127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appendix I (Convention on Migratory Species) |
E367943
|
entity |
| Predicate | categoryWithinTreaty |
P37830
|
FINISHED |
| Object | appendix listing species |
—
|
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: appendix listing species | Statement: [Appendix I (Convention on Migratory Species), categoryWithinTreaty, appendix listing species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryWithinTreaty Context triple: [Appendix I (Convention on Migratory Species), categoryWithinTreaty, appendix listing species]
-
A.
relevantSectionForTreaty
chosen
Indicates that a specific legal or textual section is pertinent or applicable to a given treaty.
-
B.
treatyScope
Indicates the range, subject matter, or extent of issues and obligations that a treaty covers or applies to.
-
C.
roleInTreaties
Indicates the specific capacity, function, or position an entity holds within the context of one or more treaties.
-
D.
treatyMention
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
-
E.
treatyOrPolicy
Indicates a formal agreement, treaty, or policy that establishes rules, obligations, or guidelines governing the relationship or behavior between entities.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.