Triple
T5323313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | global anti-nuclear movement |
E121726
|
entity |
| Predicate | reactedTo |
P767
|
FINISHED |
| Object | nuclear arms race |
—
|
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: nuclear arms race | Statement: [global anti-nuclear movement, reactedTo, nuclear arms race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactedTo Context triple: [global anti-nuclear movement, reactedTo, nuclear arms race]
-
A.
featuresReaction
Indicates that one entity exhibits, displays, or includes a particular reaction associated with another entity or context.
-
B.
reaction
Indicates a chemical or physical process in which one set of substances or conditions transforms into another, often involving interaction, change, or response between entities.
-
C.
commentedOnBy
Indicates that an entity has received a comment authored or posted by another entity.
-
D.
wasResponseTo
chosen
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
E.
reactivity
Indicates how readily one entity undergoes a chemical or physical change in response to interaction with another entity or external conditions.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 1:59 p.m.