Triple
T8595125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taisho-jima |
E203524
|
entity |
| Predicate | hasOfficialTaiwaneseClaim |
P73422
|
FINISHED |
| Object | part of Diaoyutai 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 Diaoyutai Islands | Statement: [Taisho-jima, hasOfficialTaiwaneseClaim, part of Diaoyutai Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialTaiwaneseClaim Context triple: [Taisho-jima, hasOfficialTaiwaneseClaim, part of Diaoyutai Islands]
-
A.
hasClaimOn
chosen
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by another entity.
-
C.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
D.
hasOfficialRecognition
Indicates that an entity has been formally acknowledged or approved by an authorized body or institution.
-
E.
sovereigntyClaimedFrom
Indicates that one entity asserts or has asserted sovereign authority or control that it derives from, or in place of, another entity.
- 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.