Triple
T8595124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taisho-jima |
E203524
|
entity |
| Predicate | hasOfficialChineseClaim |
P8163
|
FINISHED |
| Object | part of Diaoyu Dao (Diaoyu Islands) |
—
|
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: part of Diaoyu Dao (Diaoyu Islands) | Statement: [Taisho-jima, hasOfficialChineseClaim, part of Diaoyu Dao (Diaoyu Islands)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialChineseClaim Context triple: [Taisho-jima, hasOfficialChineseClaim, part of Diaoyu Dao (Diaoyu Islands)]
-
A.
hasChineseVersion
Indicates that an entity has a corresponding version or representation available in Chinese.
-
B.
hasOfficialRecognition
Indicates that an entity has been formally acknowledged or approved by an authorized body or institution.
-
C.
sovereignClaimedBy
chosen
Indicates that a territory or entity is asserted to be under the sovereignty or ultimate authority of a particular claimant.
-
D.
hasChineseTitle
Indicates that an entity possesses a title or name expressed in the Chinese language.
-
E.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c76fd48190ae67b660c5b8e29f |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.