Triple
T26077668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Atomic Energy Commission |
E657735
|
entity |
| Predicate | consideredProposal |
P107577
|
FINISHED |
| Object | Gromyko Plan |
—
|
NE NERFINISHED |
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: Gromyko Plan | Statement: [United Nations Atomic Energy Commission, consideredProposal, Gromyko Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredProposal Context triple: [United Nations Atomic Energy Commission, consideredProposal, Gromyko Plan]
-
A.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
B.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
C.
notableProposal
Indicates that an entity is a proposal distinguished by particular significance, impact, or recognition compared to other proposals.
-
D.
proposalProcess
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
-
E.
hasProposed
chosen
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606d0605881909bd9480afe480bd4 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:35 p.m.