Triple
T1161311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transition Radiation Detector |
E24495
|
entity |
| Predicate | distinguishesBy |
P14118
|
FINISHED |
| Object | difference in transition-radiation yield |
—
|
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: difference in transition-radiation yield | Statement: [Transition Radiation Detector, distinguishesBy, difference in transition-radiation yield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinguishesBy Context triple: [Transition Radiation Detector, distinguishesBy, difference in transition-radiation yield]
-
A.
isDistinguishedBy
chosen
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
B.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
C.
determinedBy
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
-
D.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
E.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb1915081908834ced85d09e299 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.