Triple
T4413670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein–Szilard letter |
E94911
|
entity |
| Predicate | requestedAction |
P51427
|
FINISHED |
| Object | initiation of U.S. uranium program |
—
|
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: initiation of U.S. uranium program | Statement: [Einstein–Szilard letter, requestedAction, initiation of U.S. uranium program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedAction Context triple: [Einstein–Szilard letter, requestedAction, initiation of U.S. uranium program]
-
A.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
B.
requiresActionFrom
Indicates that one entity is obligated to perform or initiate some action in response to or as a consequence of another entity or situation.
-
C.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
D.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
-
E.
refersToAction
chosen
Indicates that one entity explicitly points to, mentions, or designates a specific action or event.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e940d48190b49cca6796d60de4 |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.