Triple
T1196348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micromegas detectors |
E25675
|
entity |
| Predicate | operatingMode |
P12713
|
FINISHED |
| Object | proportional gas amplification |
—
|
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: proportional gas amplification | Statement: [Micromegas detectors, operatingMode, proportional gas amplification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingMode Context triple: [Micromegas detectors, operatingMode, proportional gas amplification]
-
A.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
hasWorkingMode
chosen
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
C.
operatingModel
Indicates how an organization structures and manages its processes, resources, and governance to deliver its products or services.
-
D.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
-
E.
operatesBase
Indicates that an organization or agent runs or manages a primary facility, location, or base of operations.
- 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.