Triple
T22927999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 釣魚臺列嶼 |
E569360
|
entity |
| Predicate | 相關國際法概念 |
P29287
|
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.
placeInInternationalLaw
chosen
Indicates that something holds a recognized status, role, or position within the framework of international law.
-
B.
internationalLawDiscussion
Indicates a relationship where entities engage in discussion or debate concerning issues, principles, or cases of international law.
-
C.
関連国境
Indicates a relationship where something is associated with, concerns, or pertains to a national border.
-
D.
roleInInternationalLaw
Indicates that an entity holds a specific function, capacity, or status within the framework, institutions, or processes of international law.
-
E.
handlesInternationalLawRelatedCases
Indicates that an entity is responsible for dealing with or managing legal cases that involve international law issues or cross-border legal matters.
- 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.