Triple
T32767893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 珠江 |
E837949
|
entity |
| Predicate | 跨境性 |
P31352
|
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.
isCrossBorder
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
B.
crossBorderRegion
chosen
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
C.
haveMajorCrossBorderOrganization
Indicates that an entity possesses or is associated with a significant organization that operates across national borders.
-
D.
hasCrossBorderTrade
Indicates that there is trade or commercial exchange occurring between entities located in different countries or jurisdictions.
-
E.
crossBorderCommunity
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.