Triple
T22927979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 釣魚臺列嶼 |
E569360
|
entity |
| Predicate | 地區爭端 |
P62867
|
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.
associatedTerritoryDispute
chosen
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
B.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
C.
regionalSecurityIssue
Indicates a security-related problem, threat, or tension that affects a specific geographic region rather than a single country or global context.
-
D.
geographicRivalry
Indicates a competitive or adversarial relationship between entities that arises from their geographic proximity, territorial interests, or spatial influence.
-
E.
conflictRegion
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180db6db88190bc8efb691dcdfdba |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:43 p.m.