Triple
T192757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z boson |
E3755
|
entity |
| Predicate | massUncertainty |
P5360
|
FINISHED |
| Object | ~0.0021 GeV/c^2 |
—
|
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: ~0.0021 GeV/c^2 | Statement: [Z boson, massUncertainty, ~0.0021 GeV/c^2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massUncertainty Context triple: [Z boson, massUncertainty, ~0.0021 GeV/c^2]
-
A.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
B.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
C.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
-
D.
magnitude
Indicates a relationship where a quantitative size, extent, or intensity is assigned to or compared between entities or values.
-
E.
isGaugeBosonOf
Indicates that one particle serves as the gauge boson mediating the fundamental interaction associated with another entity (such as a force or symmetry group).
- F. None of above. chosen
Provenance (4 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a25710bdfc81909b6697159104cf53 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.