Triple
T1184113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muon Spectrometer |
E25205
|
entity |
| Predicate | discriminates |
P1175
|
FINISHED |
| Object | muons from hadrons |
—
|
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: muons from hadrons | Statement: [Muon Spectrometer, discriminates, muons from hadrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discriminates Context triple: [Muon Spectrometer, discriminates, muons from hadrons]
-
A.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
B.
discriminatedAgainst
Indicates that one entity treats another unfairly or unequally based on a particular characteristic, such as race, gender, or other protected attributes.
-
C.
discourages
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
D.
separates
chosen
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
E.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd37b4a88190bb71a2d272c5fd1a |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.