Triple
T14565518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東沙環礁 |
E341773
|
entity |
| Predicate | 戰略位置 |
P2850
|
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.
strategicLocation
chosen
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
C.
strategicResource
Indicates that the related entity functions as a key asset whose control or availability significantly affects strategic or competitive advantage.
-
D.
strategicStance
Indicates the overarching strategic position, approach, or orientation an entity adopts in relation to others or to a particular situation.
-
E.
geopoliticalSignificance
Indicates the importance or influence that a place, event, or relationship holds within regional or global political and strategic power dynamics.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38c6350819091090ffd15772f6f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.