Triple
T28654685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天野之弥 |
E725297
|
entity |
| Predicate | 知名度の理由 |
P55574
|
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.
hasPopularityReason
chosen
Indicates that there is a specific reason or factor explaining why something is popular.
-
B.
basedOnFameFrom
Indicates that something is determined, influenced, or derived from the level or source of fame associated with an entity.
-
C.
possibleCauseOfNotability
Indicates that one entity is a potential reason or contributing factor for why another entity is notable or recognized.
-
D.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
publicRecognitionReason
Indicates the reason or basis for which an entity receives public recognition or acknowledgment.
- 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.