Triple
T14337115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ジュリアン・シュウィンガー |
E355492
|
entity |
| Predicate | 軍事研究への関与 |
P10341
|
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.
militaryInfluence
Indicates the extent to which one entity affects, shapes, or controls another entity through military power, presence, or capability.
-
B.
relatedMilitaryPlan
Indicates a relationship where one entity is associated with, derived from, or connected to a specific military plan or operation.
-
C.
involvesMilitaryChange
Indicates that the situation or event includes a modification, reorganization, or shift in military forces, structures, capabilities, or operations.
-
D.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
E.
militaryContext
chosen
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.