Triple
T1196349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micromegas detectors |
E25675
|
entity |
| Predicate | signalFormation |
P20814
|
FINISHED |
| Object | electron avalanche in amplification gap |
—
|
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: electron avalanche in amplification gap | Statement: [Micromegas detectors, signalFormation, electron avalanche in amplification gap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalFormation Context triple: [Micromegas detectors, signalFormation, electron avalanche in amplification gap]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
C.
formationMechanism
chosen
Indicates the process or mechanism by which something is formed, created, or brought into existence.
-
D.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
formationPrinciple
Indicates the underlying rule, pattern, or principle according to which something is formed, structured, or brought into existence.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd7a756c819085d695acfffeaceb |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.