Triple
T28654680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天野之弥 |
E725297
|
entity |
| Predicate | 関係分野 |
P6979
|
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.
relatedField
chosen
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
B.
relatedWorkField
Indicates that one work is associated with or pertains to the same or a relevant field, discipline, or area of activity as another work.
-
C.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
D.
fieldOfCooperation
Indicates a cooperative relationship in which two or more entities work together within a particular domain, discipline, or area of activity.
-
E.
associatedScholarlyField
Indicates that one entity is connected to or concerned with a particular scholarly or academic field of study.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:54 a.m.