Triple
T37547180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中沙群岛 |
E933494
|
entity |
| Predicate | 地缘战略意义 |
P12069
|
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.
geopoliticalSignificance
chosen
Indicates the importance or influence that a place, event, or relationship holds within regional or global political and strategic power dynamics.
-
B.
geopoliticalScope
Indicates the geographic or political area within which an entity’s authority, relevance, or effect is defined or applies.
-
C.
geopoliticalFactor
Indicates a relationship where one entity influences or shapes another through political, territorial, or international power dynamics and conditions.
-
D.
geopoliticalObjective
Indicates a relationship where an actor pursues, holds, or is associated with a strategic political or territorial goal at the level of states or regions.
-
E.
geopoliticalFlank
Indicates a strategic positional relationship where one geopolitical entity is located to the side of, and can influence or threaten, another in a military or political sense.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.