Triple
T6432267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z′ bosons |
E129805
|
entity |
| Predicate | massProperty |
P70585
|
FINISHED |
| Object | heavier than the Standard Model Z boson |
—
|
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: heavier than the Standard Model Z boson | Statement: [Z′ bosons, massProperty, heavier than the Standard Model Z boson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massProperty Context triple: [Z′ bosons, massProperty, heavier than the Standard Model Z boson]
-
A.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
B.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
C.
obtainsMassVia
Indicates that an entity acquires its mass through a specified process, mechanism, or interaction.
-
D.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
E.
mechanicalProperty
Indicates a relationship where a mechanical characteristic (such as strength, stiffness, hardness, or elasticity) is attributed to or associated with an entity.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693cadf08190aca84888a3440b3d |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:44 p.m.