Triple
T28654679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天野之弥 |
E725297
|
entity |
| Predicate | 関係国際機関 |
P11210
|
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.
internationalInstitutionRelationship
Indicates a relationship in which one entity is connected to, interacts with, or is associated with an international institution (such as through membership, partnership, oversight, or collaboration).
-
B.
involvedInternationalOrganization
chosen
Indicates that an entity participates in, is affiliated with, or plays a role within an international organization.
-
C.
worldAssociation
Indicates a broad, often global-level connection or affiliation between entities, such as membership, involvement, or linkage within a worldwide context.
-
D.
hasInternationalRelation
Indicates that one entity maintains some form of official or recognized international relationship or interaction with another entity.
-
E.
internationalOrganizationStatus
Indicates that an entity holds a recognized status or role within an international organization.
- 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.