Triple
T23269635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GALLEX |
E588251
|
entity |
| Predicate | detectionReaction |
P83078
|
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: [GALLEX, detectionReaction, 71Ga(νe,e−)71Ge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectionReaction Context triple: [GALLEX, detectionReaction, 71Ga(νe,e−)71Ge]
-
A.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
B.
containsReaction
Indicates that one entity includes or encompasses a specific reaction as part of its contents or structure.
-
C.
reactionToRecognition
Indicates how an entity responds or behaves when it receives recognition, acknowledgment, or praise from another entity.
-
D.
startsWithReaction
Indicates that one entity begins with, or is initiated by, a specified reaction or responsive event.
-
E.
sensingAction
chosen
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
- 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_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. |
Created at: April 17, 2026, 4:45 p.m.