Triple
T1166284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMS experiment |
E24805
|
entity |
| Predicate | detectorMass |
P18001
|
FINISHED |
| Object | about 14,000 tonnes |
—
|
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: about 14,000 tonnes | Statement: [CMS experiment, detectorMass, about 14,000 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectorMass Context triple: [CMS experiment, detectorMass, about 14,000 tonnes]
-
A.
massUncertainty
Indicates that there is a quantified degree of uncertainty or imprecision associated with the mass value of an entity or system.
-
B.
massParameter
chosen
Indicates a relationship where a specific mass value is assigned to or characterizes an entity as a parameter in a model or system.
-
C.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
D.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
E.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.