Triple
T1755191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear Non-Proliferation Treaty |
E38533
|
entity |
| Predicate | firstReviewConferenceHeldIn |
P32792
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Nuclear Non-Proliferation Treaty, firstReviewConferenceHeldIn, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReviewConferenceHeldIn Context triple: [Nuclear Non-Proliferation Treaty, firstReviewConferenceHeldIn, 1975]
-
A.
originalConference
Indicates that an entity was first presented, published, or introduced at a particular conference.
-
B.
firstEditionHeldIn
Indicates the location where the first edition or initial occurrence of an event was held.
-
C.
firstSessionHeldIn
Indicates that the initial or inaugural session of an event, activity, or process took place in a specified location or context.
-
D.
conferenceAtTheTime
Indicates that an event or situation occurs during the time period in which a specified conference is taking place.
-
E.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba6a63f588190b53b39c6b97d74f4 |
completed | March 7, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69aa61c7ef4c8190abec87c96a787d82 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba6a4c84c8190b3ce0bf69c2b5f6d |
completed | March 7, 2026, 4:16 a.m. |
Created at: March 4, 2026, 7:31 p.m.