Triple
T29610148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 巴士海峽 |
E754691
|
entity |
| Predicate | 相關國家專屬經濟區 |
P2047
|
FINISHED |
| Object | 台灣專屬經濟區 |
—
|
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: 台灣專屬經濟區 | Statement: [巴士海峽, 相關國家專屬經濟區, 台灣專屬經濟區]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 相關國家專屬經濟區 Context triple: [巴士海峽, 相關國家專屬經濟區, 台灣專屬經濟區]
-
A.
countryExclusiveEconomicZone
chosen
Indicates that a specified maritime area lies within the exclusive economic zone legally designated to a particular country.
-
B.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
C.
exclusiveEconomicZoneBasis
Indicates that one entity’s exclusive economic zone is established, defined, or justified on the basis of its relationship to another entity (such as a land territory, maritime feature, or baseline).
-
D.
EEZArea
Indicates that an area lies within a country's Exclusive Economic Zone (EEZ), where that state has special rights over marine resources and activities.
-
E.
neighboringEEZ
Indicates that the exclusive economic zones (EEZs) of two maritime areas are adjacent or share a common boundary.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66dea375881909684db997861425c |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:28 p.m.