Triple
T3411675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝永振一郎 |
E71909
|
entity |
| Predicate | 主な業績 |
P36130
|
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.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
B.
notableDeed
chosen
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
C.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
D.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
E.
majorOperationsOf
Indicates that one entity is a primary or significant operation, activity, or functional undertaking associated with 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb90a76288190b92ef3b26638cd47 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.