Triple
T26698953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNCLOS Part V |
E673098
|
entity |
| Predicate | adoptedWithUNCLOS |
P49032
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [UNCLOS Part V, adoptedWithUNCLOS, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedWithUNCLOS Context triple: [UNCLOS Part V, adoptedWithUNCLOS, 1982]
-
A.
statusUnderUNCLOS
Indicates the legal status or classification of an entity as defined under the United Nations Convention on the Law of the Sea (UNCLOS).
-
B.
adoptedWithTreaty
chosen
Indicates that something (such as a policy, measure, or standard) was formally adopted as part of, or through the ratification of, a specific treaty.
-
C.
featureTypeUnderUNCLOS
Indicates that one geographic or maritime feature is classified according to a specific feature type as defined under the United Nations Convention on the Law of the Sea (UNCLOS).
-
D.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
E.
appliesToTerritorialWatersOf
Indicates that something (such as a rule, status, or condition) is applicable within the territorial waters of a specified 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 3:30 a.m.