Triple
T38675511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ren’ai Jiao (China) |
E943728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disputed maritime feature |
C5772
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: disputed maritime feature Context triple: [Ren’ai Jiao (China), instanceOf, disputed maritime feature]
-
A.
maritime boundary decision
A maritime boundary decision is a formal determination, typically by a court, tribunal, or negotiated agreement, that defines the spatial limits and legal rights of states over adjacent or overlapping maritime zones such as territorial seas, exclusive economic zones, and continental shelves.
-
B.
maritime territories
Maritime territories are sea areas over which a state exercises legal rights and jurisdiction, including territorial waters, exclusive economic zones, and related maritime zones.
-
C.
maritime zone
A maritime zone is a legally defined area of the sea, measured from a coastal state's baseline, within which specific rights, jurisdiction, and responsibilities are allocated under international law.
-
D.
maritime boundary delimitation case
A maritime boundary delimitation case is a legal dispute or proceeding in which states seek the determination or adjustment of their respective maritime zones and boundaries, such as territorial seas, exclusive economic zones, and continental shelves, in accordance with international law.
-
E.
disputed territory
chosen
A disputed territory is a geographic area over which two or more parties claim sovereignty or control, without mutual agreement on its legal or political status.
- F. None of above.
Provenance (1 batch)
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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.