Triple
T29610137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 巴士海峽 |
E754691
|
entity |
| Predicate | 戰略意義 |
P19259
|
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.
strategicImportanceDueTo
Indicates that one entity possesses strategic significance specifically as a result of its connection, characteristics, or influence related to another entity.
-
B.
strategicAspect
Indicates that something pertains to a strategic dimension, such as long-term planning, positioning, or high-level decision-making within a broader context.
-
C.
militaryImportance
chosen
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
-
D.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
E.
eraOfStrategicImportance
Indicates that a particular time period holds significant strategic value or influence within a broader historical, political, or organizational context.
- 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.