Triple
T23269693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNO |
E588252
|
entity |
| Predicate | usedReaction |
P151617
|
FINISHED |
| Object | 71Ga(νe,e−)71Ge |
—
|
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: 71Ga(νe,e−)71Ge | Statement: [GNO, usedReaction, 71Ga(νe,e−)71Ge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedReaction Context triple: [GNO, usedReaction, 71Ga(νe,e−)71Ge]
-
A.
receivedReaction
Indicates that an entity has been the target of a reaction or response from another entity.
-
B.
relatedReaction
Indicates that one reaction is connected or associated with another reaction in some relevant way.
-
C.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
D.
netReaction
Indicates the overall chemical transformation resulting from combining all individual reaction steps, showing only the net change between reactants and products.
-
E.
isAReactionTo
Indicates that one event, action, or state occurs as a direct response or consequence of another.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957324bc8190b8b53d4b18386151 |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:45 p.m.