Triple
T4053646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukawa potential |
E84642
|
entity |
| Predicate | rangeControlledBy |
P53029
|
FINISHED |
| Object | inverse of screening parameter 1/\mu |
—
|
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: inverse of screening parameter 1/\mu | Statement: [Yukawa potential, rangeControlledBy, inverse of screening parameter 1/\mu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeControlledBy Context triple: [Yukawa potential, rangeControlledBy, inverse of screening parameter 1/\mu]
-
A.
recognizedControlOf
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control over something.
-
B.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
C.
speciesControlled
Indicates that one entity exerts control, management, or regulatory influence over a particular species.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9fcb31c819098d5287b6fc84f4e |
completed | March 9, 2026, 4:49 p.m. |
Created at: March 9, 2026, 3:37 p.m.