Triple
T1184085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muon Spectrometer |
E25205
|
entity |
| Predicate | coversPseudorapidityRange |
P5344
|
FINISHED |
| Object | -4.0 < η < -2.5 |
—
|
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: -4.0 < η < -2.5 | Statement: [Muon Spectrometer, coversPseudorapidityRange, -4.0 < η < -2.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversPseudorapidityRange Context triple: [Muon Spectrometer, coversPseudorapidityRange, -4.0 < η < -2.5]
-
A.
pseudorapidityCoverage
chosen
Indicates the range of particle pseudorapidity values over which a detector, measurement, or analysis is sensitive or applicable.
-
B.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
C.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
D.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
-
E.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
- 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.