Triple
T34585378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W and Z bosons |
E888029
|
entity |
| Predicate | areForceCarriersFor |
P3988
|
FINISHED |
| Object | weak interaction |
—
|
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: weak interaction | Statement: [W and Z bosons, areForceCarriersFor, weak interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areForceCarriersFor Context triple: [W and Z bosons, areForceCarriersFor, weak interaction]
-
A.
hasForceCarrier
Indicates that a fundamental interaction or force is mediated or carried by a specific particle or field.
-
B.
isGaugeBosonOf
chosen
Indicates that one particle serves as the gauge boson mediating the fundamental interaction associated with another entity (such as a force or symmetry group).
-
C.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
D.
usesForcesFrom
Indicates that one entity applies or derives physical forces from another entity as part of its operation or behavior.
-
E.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c7ea608190bd92d69643330823 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.