Triple
T37600683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongsha Islands |
E935513
|
entity |
| Predicate | maritimeClaimsRelatedTo |
P48030
|
FINISHED |
| Object | exclusive economic zone |
—
|
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: exclusive economic zone | Statement: [Zhongsha Islands, maritimeClaimsRelatedTo, exclusive economic zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeClaimsRelatedTo Context triple: [Zhongsha Islands, maritimeClaimsRelatedTo, exclusive economic zone]
-
A.
maritimeClaimBasis
Indicates the legal or factual grounds on which a party bases its claim to maritime zones, rights, or jurisdiction.
-
B.
maritimeClaimType
chosen
Indicates the specific nature or category of a party’s asserted rights or jurisdiction over a maritime area.
-
C.
maritimeDispute
Indicates a contested claim or disagreement between parties over maritime areas, boundaries, or rights.
-
D.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
-
E.
maritimeIncident
Indicates an event or situation involving a vessel or maritime activity that results in damage, danger, or disruption at sea or in navigable waters.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.