Triple
T6596540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seabed Disputes Chamber |
E148489
|
entity |
| Predicate | canBeSeisedBy |
P35349
|
FINISHED |
| Object | States Parties |
—
|
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: States Parties | Statement: [Seabed Disputes Chamber, canBeSeisedBy, States Parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSeisedBy Context triple: [Seabed Disputes Chamber, canBeSeisedBy, States Parties]
-
A.
canBeSeizedBy
chosen
Indicates that one entity is legally or physically able to be taken control of, captured, or confiscated by another entity.
-
B.
canBeSuedFor
Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
-
C.
canBeSuedAs
Indicates that one entity has legal standing or capacity to be the target of a lawsuit initiated by another entity.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canOwn
Indicates that one entity is permitted or legally able to possess or hold ownership rights over 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.