Triple
T37547187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中沙群岛 |
E933494
|
entity |
| Predicate | 相关国际法框架 |
P29287
|
FINISHED |
| Object | 《联合国海洋法公约》 |
—
|
NE NERFINISHED |
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.
roleInInternationalLaw
Indicates that an entity holds a specific function, capacity, or status within the framework, institutions, or processes of international law.
-
D.
internationalAgreementBasis
Indicates that one entity serves as the legal or formal basis for an international agreement involving another entity.
-
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_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.