Triple
T3921415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi constant |
E88966
|
entity |
| Predicate | roleInStandardModel |
P8683
|
FINISHED |
| Object | sets overall scale of weak interaction strength |
—
|
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: sets overall scale of weak interaction strength | Statement: [Fermi constant, roleInStandardModel, sets overall scale of weak interaction strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInStandardModel Context triple: [Fermi constant, roleInStandardModel, sets overall scale of weak interaction strength]
-
A.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
B.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
C.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
definesRole
chosen
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.