Triple
T797283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo Szilard |
E17050
|
entity |
| Predicate | conceived |
P119
|
FINISHED |
| Object | idea of a nuclear chain reaction |
—
|
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: idea of a nuclear chain reaction | Statement: [Leo Szilard, conceived, idea of a nuclear chain reaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceived Context triple: [Leo Szilard, conceived, idea of a nuclear chain reaction]
-
A.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
B.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
C.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
D.
theorized
chosen
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
E.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b342888190a344fe81a2c9f33c |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.