Triple
T26117129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Part IV of UNCLOS |
E658852
|
entity |
| Predicate | legalRegimeFor |
P12605
|
FINISHED |
| Object | archipelagic States |
—
|
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: archipelagic States | Statement: [Part IV of UNCLOS, legalRegimeFor, archipelagic States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRegimeFor Context triple: [Part IV of UNCLOS, legalRegimeFor, archipelagic States]
-
A.
governedByLegalRegime
chosen
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
B.
countryLegalFramework
Indicates the legal system, regulations, and institutional rules that govern actions and relationships within a given country.
-
C.
legalCodeAppliesTo
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
-
D.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
-
E.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 26, 2026, 8:06 p.m.