Triple
T53729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAUD Committee |
E1058
|
entity |
| Predicate | concluded |
P2540
|
FINISHED |
| Object | an atomic bomb was technically feasible |
—
|
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: an atomic bomb was technically feasible | Statement: [MAUD Committee, concluded, an atomic bomb was technically feasible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concluded Context triple: [MAUD Committee, concluded, an atomic bomb was technically feasible]
-
A.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
B.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
C.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
- F. None of above. chosen
Provenance (4 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24b39eef081909cec4333f2b25513 |
completed | Feb. 28, 2026, 1:56 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.